Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.8.1
-
None
-
None
-
Docs Required, Release Notes Required
Description
There seems to be two conflicting documentation on loading the plugin
provider :
1. The first way as shown in this documentation
https://apacheignite.readme.io/docs/plugins :
uses the Java Service Loader to load the plugin provider . It loads the
plugin configurations through the ignite configuration and hence needs to
use getPluginConfigurations to get the right configuration for the plugin.
Concern : igniteconfiguration.getPluginConfigurations is deprecated in
2.8.1
2. The second way : igniteconfiguration.getPluginConfigurations has been
deprecated in 2.8.1 . The recommended way of sending configuration is by
calling igniteconfiguration.setPluginProvider .
Please note there was no 'setPluginProvider' method in the versions prior to
2.8.1.
(
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#getPluginConfigurations--
)
Concern : 2.8.1 plugin documentation talks about using service loader
framework. https://apacheignite.readme.io/docs/plugins. If we use
setPluginProvider, there is no need to load plugin provider through java
service loader.
As per the latest conversation on Ignite Users , it was suggested that I raise a documentation improvement to use the approach 2 above . This Jira is to change the documentation at https://apacheignite.readme.io/docs/plugins so that it reflects approach 2.
http://apache-ignite-users.70518.x6.nabble.com/2-8-1-Loading-Plugin-Provider-td33370.html