I understand that there is a jetty plugin for elasticsearch, which enables
us to run ES in a jetty container instead of using Netty for HTTP.
Is there a way for us to bundle elasticsearch and run it on an existing
jetty instance, instead of spawning a new jetty instance?
The idea is for us to use a wrapper REST service (which contains business
model and logic), that talks to elasticsearch for indexing and searching
capabilities.
We may want to interact with ES cluster using the Java Client from the
wrapper REST service
For the monitoring and administration, we may want to enable HTTP in a
single node, and run it on the container where the wrapper REST service
exists.
Look at the wares plugin. It enables building an ES node as a war that can
be deployed into a webapp container like Jetty, Tomcat, Glassfish, or
Wildfly, with executing a wrapper REST service, for example with Jersey.
I submitted some useful addings for ready-to-deploy
Of course you have to modify that for your favorite war deploy environment
and solution.
Look at the wares plugin. It enables building an ES node as a war that can
be deployed into a webapp container like Jetty, Tomcat, Glassfish, or
Wildfly, with executing a wrapper REST service, for example with Jersey.
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.