You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project that works fine using elastisch 1.0.2 and datomic-free 0.8.3848 against an elasticsearch 0.90.0.RC1 server (since 0.20.x and 0.90.0.Beta).
Datomic currently seems to depend on Lucene 3.x API, and specifically includes lucene-core 3.3.0.
lein classpath only shows lucene-core 3.3.0, no other lucene or elasticsearch jars.
I tried switching to elastisch 1.1.0-beta2 to see if is was compatible. It pulls down ES 0.90.0.Beta1 and Lucene 4.1. Now Datomic is having problems and the project won't start. Also, lein classpath shows lots of lucene jars and the full elasticsearch jar.
Is this just beta related, or will the native client in elastisch depend on all these jars?
Will there be a method to avoid pulling in lucene/elasticsearch jars at all and maintain Datomic compatibility until they upgrade to 4.x?
The text was updated successfully, but these errors were encountered:
If you don't need the native client, exclude it from Elastisch's dependencies using the :exclusions option. ElasticSearch uses Lucene
version they need/want, and it's up to Datomic to catch up and/or support the version ES uses.
(But for those who need/want the native client, one can hope that ES will package it in a separate, smaller jar to avoid pulling in full ES and the Lucene dependencies.)
I have a project that works fine using elastisch 1.0.2 and datomic-free 0.8.3848 against an elasticsearch 0.90.0.RC1 server (since 0.20.x and 0.90.0.Beta).
Datomic currently seems to depend on Lucene 3.x API, and specifically includes lucene-core 3.3.0.
lein classpath only shows lucene-core 3.3.0, no other lucene or elasticsearch jars.
I tried switching to elastisch 1.1.0-beta2 to see if is was compatible. It pulls down ES 0.90.0.Beta1 and Lucene 4.1. Now Datomic is having problems and the project won't start. Also, lein classpath shows lots of lucene jars and the full elasticsearch jar.
Is this just beta related, or will the native client in elastisch depend on all these jars?
Will there be a method to avoid pulling in lucene/elasticsearch jars at all and maintain Datomic compatibility until they upgrade to 4.x?
The text was updated successfully, but these errors were encountered: