Hi Ivan,
i was aware of that thread i also asked to learn about overriding
DefaultSimilarity stuff or similar other approach.
Thanks.
On 30/04/2013 17:24, Ivan Brusic wrote:
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 boosts in 4.x.
Cheers,
Ivan
On Tue, Apr 30, 2013 at 7:45 AM, Tamer Gür <t...@ebi.ac.uk> wrote:
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
feasible for us since we have many indexes and complex fields.
So what is possible drawback if i override DefaultSimilarity and put back
the Document.setBoost() during norm calculation?
or is there any other way to add a scalar factor to all document?
Thank you.
Tamer
------------------------------**------------------------------**---------
To unsubscribe, e-mail:
java-user-unsubscribe@lucene.**apache.org<java-user-unsubscr...@lucene.apache.org>
For additional commands, e-mail:
java-user-help@lucene.apache.**org<java-user-h...@lucene.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
