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/<plugin>/. 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? thanks, marko -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4028e9d5-222a-46f1-a403-e2f32102c988%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
