I'm considering replacing a Compass-based search in one of our
applications with an ElasticSearch-based equivalent. It's looking very
promising, however I'm concerned at the presence of Lucene classes
inside the elasticsearch-0.14.2 JAR. The Compass application
obviously has its own Lucene 2.x JARs, and there's a real danger of
My hope would be to ElasticSearch's java TransportClient to
communicate with the server, and I'd have thought there was no need
for it to have any knowledge of Lucene.
Would it be practical to repackage the ElasticSearch JARs to separate
the client code from the core ElasticSearch server code?
I could use the REST interface, I suppose, but I rather like the
java client, it'd be a shame to lose that.