I have been using embedded ES nodes as a mean of easily unit/integration
testing my search client code. But now I have a custom Native Script plugin
and I was how I could tell the embedded ES node to use the custom Native
Plugin.
Is it as simple as giving it a Settings with
"script.native.myplugin.type: com.whatever.MyPluginFactory"?
When deploying the plugin to ES it needs to be under a subdirectory of
plugin directory named "myplugin" as named above. Does this still matter or
is it enough to have the MyPlugin jar in the maven dependencies (i.e.
classpath)?
I have been using embedded ES nodes as a mean of easily unit/integration
testing my search client code. But now I have a custom Native Script plugin
and I was how I could tell the embedded ES node to use the custom Native
Plugin.
Is it as simple as giving it a Settings with
"script.native.myplugin.type: com.whatever.MyPluginFactory"?
When deploying the plugin to ES it needs to be under a subdirectory of
plugin directory named "myplugin" as named above. Does this still matter or
is it enough to have the MyPlugin jar in the maven dependencies (i.e.
classpath)?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.