Support for ElasticSearch v5 ? about dropwizard-elasticsearch HOT 3 OPEN

I've been looking into this, and while the transport client is a fairly trivial change, the node client is not.

In addition, changes to the way ES is built are making it difficult to test in a packaged Dropwizard application:

• there's an explicit reliance on log4j2 which can't (as far as I can see) be overridden by adding slf4j bridging.
• the Build class in ES now reads its build information from the Manifest file. When you build a single jar for your Dropwizard app, this information is lost, and the Node client complains that it can't be read.

As I say, the changes to the Transport client are fairly trivial, and seem to work as expected. My work so far is here, if anyone is interested: https://github.com/mattflax/dropwizard-elasticsearch/tree/elasticsearch-5.0

from dropwizard-elasticsearch.

+1

@mattflax thanks for your solution!

from dropwizard-elasticsearch.

I've ended up disabling the NodeClient completely - Elastic reckon you should run a local coordinating node, and use the TransportClient to communicate with that. You can still use the setting at this stage, but it will throw an error.

There's currently an error from log4j2 when starting the Dropwizard application - I can't figure out a way around that which doesn't break the Elasticsearch client classes (which rely specifically on log4j2).

Do let me know if you have advice on better approaches to this issue - the approach I've ended up with feels a bit ham-fisted, so better suggestions would be appreciated!

from dropwizard-elasticsearch.