Configuration for explicit plugins providing.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Configuration for explicit plugins providing.

Mikhail Petrov
Hi Igniters!

Now plugin loading is based on presence of plugin class name in
META-INF/service/org.apache.ignite.plugin.PluginProvider file. I propose to
add special configuration in IgniteConfiguration for passing needed plugin
instances explicitly. It provides ability to
    1. specify plugins via spring configuration.
    2. avoid storing PluginConfiguration separately from PluginProvider
(Now all PluginConfiguration are stored as an array in IgniteConfiguration
and plugin if it's needed in PluginConfiguration merely iterates over all
configurations) by passing plugin configuration directly into plugin
provider.
It's possible to support both of approaches for backward compatibility
(e.g. if plugins is not set via IgniteConfiguration current approach will
be used).

PR -- https://github.com/apache/ignite/pull/6517
<https://github.com/apache/ignite/pull/6517>
JIRA -- https://issues.apache.org/jira/browse/IGNITE-11744

I would like to receive feedback on this feature concept.
Reply | Threaded
Open this post in threaded view
|

Re: Configuration for explicit plugins providing.

Anton Vinogradov-2
+1 to simplification.

On Mon, Apr 29, 2019 at 3:32 PM Mikhail Petrov <[hidden email]>
wrote:

> Hi Igniters!
>
> Now plugin loading is based on presence of plugin class name in
> META-INF/service/org.apache.ignite.plugin.PluginProvider file. I propose to
> add special configuration in IgniteConfiguration for passing needed plugin
> instances explicitly. It provides ability to
>     1. specify plugins via spring configuration.
>     2. avoid storing PluginConfiguration separately from PluginProvider
> (Now all PluginConfiguration are stored as an array in IgniteConfiguration
> and plugin if it's needed in PluginConfiguration merely iterates over all
> configurations) by passing plugin configuration directly into plugin
> provider.
> It's possible to support both of approaches for backward compatibility
> (e.g. if plugins is not set via IgniteConfiguration current approach will
> be used).
>
> PR -- https://github.com/apache/ignite/pull/6517
> <https://github.com/apache/ignite/pull/6517>
> JIRA -- https://issues.apache.org/jira/browse/IGNITE-11744
>
> I would like to receive feedback on this feature concept.
>