Re: Recovery failed : IllegalArgumentException[No enum constant org.apache.lucene.util.Version.4.3.1]

Hey, thanks for raising this. The exception is extremely helpful. This boils down to a bug / inconsistency in Lucene where some of the bugfix releases ie. 3.6.1, 4.3.1, 4.5.1 did specify the minor version in it's version constant where is shouldn't. I just opened [1] that fixes the issue. It's

Re: Recovery failed : IllegalArgumentException[No enum constant org.apache.lucene.util.Version.4.3.1]

Thanks Simon. We tested with latest build (1.3.1 SNAPSHOT). *All our old data (0.90.2) got recovered without any issues in 1.3.1.*. Thanks Pounraj Manikandan -- View this message in context:

Re: Recovery failed : IllegalArgumentException[No enum constant org.apache.lucene.util.Version.4.3.1]

FYI 1.3.1 has been release http://t.co/rCL9rAofta go ahead unless you wanna run on 1.3.1-SNAPSHOT thanks for raising this again! simon On Monday, July 28, 2014 5:17:46 PM UTC+2, Manikandan Pounraj wrote: Thanks Simon. We tested with latest build (1.3.1 SNAPSHOT). *All our old data

Re: Recovery failed : IllegalArgumentException[No enum constant org.apache.lucene.util.Version.4.3.1]

This will really help us lot. Thank you. Pounraj Manikandan -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Recovery-failed-IllegalArgumentException-No-enum-constant-org-apache-lucene-util-Version-4-3-1-tp4060560p4060743.html Sent from the ElasticSearch Users

Recovery failed : IllegalArgumentException[No enum constant org.apache.lucene.util.Version.4.3.1]

Hello Team, We are using Elastic search for last 2years and we are currently in 0.90.2 release which was upgraded on Jan 2014. For our requirement aggregation (top_hits) fits and we planned to upgrade to 1.3.0 We are getting following exception when elastic search tries to recover shards.