I'm planning to embed a full ES server within a custom application. ES
customization will be implemented through the ES plugins mechanism. The
plan is to create a single runnable jar that would include all the ES +
plugin dependencies. A custom main class would automatically setup
environment specific configuration and then start up ES bootstrap class.
It seems that the plugin code can be bundled in a single jar with the rest
of ES + libs, provided that all the es-plugin.properties files can be
loaded from plugins//.
I'm using the sbt build tool which fetches elasticsearch.jar from Maven
repository. I noticed that some of the jars that are included with the ES
distribution package are marked as optional, compile-time dependencies and
are not included in my package.
Is there any documentation about when a particular optional dependency is
needed?
Is this type of embedding approach suitable to be used with ES?
Any caveats to be aware of?
About optional dependencies, I have seen in the past some things around groovy and geo stuff.
So basically, if you don’t use scripts in your embedded app or any Spatial4J related types, you can probably omit them.
Embedding elasticsearch can work IMHO. But be aware that your application is also running in the same JVM, that you are may be deploying this in a container (Tomcat/JBoss/Whatever) so you are subject to GC generated by those layers as well. If your application is not overloaded, you can probably do this.
If you are touching the limit, you could at some point transform your embedded Node to a Client Node or replace with a Transport Client and run elasticsearch in its own process.
I'm planning to embed a full ES server within a custom application. ES customization will be implemented through the ES plugins mechanism. The plan is to create a single runnable jar that would include all the ES + plugin dependencies. A custom main class would automatically setup environment specific configuration and then start up ES bootstrap class.
It seems that the plugin code can be bundled in a single jar with the rest of ES + libs, provided that all the es-plugin.properties files can be loaded from plugins//.
I'm using the sbt build tool which fetches elasticsearch.jar from Maven repository. I noticed that some of the jars that are included with the ES distribution package are marked as optional, compile-time dependencies and are not included in my package.
Is there any documentation about when a particular optional dependency is needed?
Is this type of embedding approach suitable to be used with ES?
Any caveats to be aware of?
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.