Hallo Nischal,
it looks like your classpath contains different Lucene versions mixed together.
Lucene 4.4 would never use the old Lucene40Codec for writing a new index, so it
looks like the SPI framework chooses an older index version by default (the one
of another Lucene version on the classpa
Hi,
I am using lucene in my eclipse plugin, while initializing the
IndexConfigWriter i am getting an exception (see below). Interesting part
is when i am running a test.java class in the same plugin (with a main
method with call to the same method) everything is working fine.
But when i run the pl
Hi,
I am using lucene in my eclipse plugin, while initializing the
IndexConfigWriter i am getting an exception (see below). Interesting part
is when i am running a test.java class in the same plugin (with a main
method with call to the same method) everything is working fine.
But when i run the pl
Hello.
Code Sample for the issue:-
Would like to mention that I am able to index documents containing close
to 3.5 Lakh lines.. Whereas INDEXING is NOT happening when number of
lines are anything greater than 5 Lakhs.. I get Memory Exception from
Java...
Would sincerely appreciate some help
Hi,
On Sat, Aug 31, 2013 at 6:55 AM, Rose, Stuart J wrote:
> I've noticed that processes that were previously IO bound (in 3.5) are now
> CPU bound (in 4.4) and I expect it is due to the compression/decompression of
> term vector fields in 4.4.
>
> It would be nice if users of 4.4 could turn t
