Maybe double check your CLASSPATHs?
Because, based on the line numbers in the exception, it really looks
like it's Lucene 2.1 that's trying to open a Lucene 2.2+ index. The
term infos file (.tii, .tis) changed from -2 -> -3 format in 2.3.
Mike
On Feb 25, 2008, at 7:19 AM, Paul Danese wro
2Unfortunately, the answer is "no". I didn't use an upgraded version of lucene
or solr. this is the bizzarre issue. I'm actually using solr via the
acts_as_solr plugin used in ruby.
At the time, I was adding a few 100-thousand docs to the index...there appears
to have been a memory leak as
did you create/modify the index with a newer version of lucene than the
one you use in solr?
In this case I doubt you can downgrade your index, but maybe you can
upgrade lucene in your solr (search in this forum, there should be a
thread about this), (or try with the latest nightly builds)
Pau
2Hi all,
Is there any way to recover from such an error as listed in the subject heading?
Luke can view the index just fine (at least at a cursory level Luke is able to
open the index, give me back the # of docs, etc.), but solr throws this
exception whenever I try and start it up.
any ideas o
