Hi, Unfortunately the GridQueryProcessor was not designed to be pluggable, but it seems to me that among the best option that you might have is to implement PluginProcessor and IgnitePlugin and do it there. Another option is to implement LifecycleBean and rely on AFTER_NODE_START event that is processed synchronously right before the end of IgniteKernal.start().
Here a couple of references to classes that might be useful for understanding the plugin approach in case you will go this way: https://github.com/apache/ignite/blob/master/modules/direct-io/src/main/java/org/apache/ignite/internal/processors/cache/persistence/file/LinuxNativeIoPluginProvider.java https://github.com/apache/ignite/blob/master/modules/direct-io/src/main/java/org/apache/ignite/internal/processors/cache/persistence/file/LinuxNativeIoPlugin.java Lifecycle bean is pretty straightforward to use, and even has an example: https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/misc/lifecycle/LifecycleExample.java But anyway, since query processor was not designed this way, I would do a proper test to see if this may work. Best regards, Anton -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
