Hello all,
We've just upgraded to 4.2 from 3.6 and suffered some performance degradation
in both indexing and retrieval. We've had to eliminate compression, even
supplying our own NoCompression codec since there doesn't appear to be any
built in support for this. Hopefully we're not overlooki
There was a similar question asked a couple of months ago, with a great
answer by Uwe Schindler:
http://search-lucene.com/m/Z2GP220szmS&subj=RE+What+is+equivalent+to+Document+setBoost+from+Lucene+3+6+inLucene+4+1+
I am still on Lucene 3.x, so I have not yet had a chance to mimic document
level bo
Hi,
we are migrating from 3.6 to 4.2. since Document.setBoost() method
removed we are trying to reimplement.
Currently we are using Document.setBoost() method as a scalar boost
factor across our multiple different indexes.
With the lucene 4.2 setting this factor by field.setBoost() is not