Lucene Runtime Dependency in Transport Mode

I'm having a conflict running elasticsearch and neo4j together. Even
running ElasticSearch in transport mode requires the Lucene jars, but only
the Version class in org.apache.lucene.util.Lucene. It would be nice if
elasticsearch could run in transport mode with no Lucene dependencies. Is
there any other way around this?

Thanks,
Eric

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

I'm working on an alternative approach to the current ES code, so you can
choose between ES clients: (bulk) index only for ingesting (for example
push clients), query only (to deny modifications), index and query, or full
admin access client.

Also I want to implement a Java TransportClient API wrapper around Netty
HTTP/Websocket connections to get rid of the JVM compatibility and Zen
discovery ES version issues (comparable to Perl/Python/Ruby client via
HTTP). For query clients, the Lucene query jars are always required.

In my experiments some time ago on 0.20 codebase I created a simple ES Java
ingest client with 2 MB size only.

Sorry, there is no quick result available yet. My approach requires
thorough modularization of the current ES codebase, and takes some time, I
do it in my spare time.

Jörg

On Wed, Jul 24, 2013 at 6:44 AM, ericm.infusionsoft@gmail.com wrote:

I'm having a conflict running elasticsearch and neo4j together. Even
running ElasticSearch in transport mode requires the Lucene jars, but only
the Version class in org.apache.lucene.util.Lucene. It would be nice if
elasticsearch could run in transport mode with no Lucene dependencies. Is
there any other way around this?

Thanks,
Eric

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

I would be happy if ES shaded the Lucene jars, they do it for the netty and
other libraries, I'm not sure why they don't do it for Lucene unless the
Lucene API leaks out of the ES one (that is, a client of ES needs to refer
to Lucene code as part of interacting with it).

On 24 July 2013 14:44, ericm.infusionsoft@gmail.com wrote:

I'm having a conflict running elasticsearch and neo4j together. Even
running ElasticSearch in transport mode requires the Lucene jars, but only
the Version class in org.apache.lucene.util.Lucene. It would be nice if
elasticsearch could run in transport mode with no Lucene dependencies. Is
there any other way around this?

Thanks,
Eric

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.