). Is there a
better solution?
Thanks,
Murali
--
View this message in context:
http://www.nabble.com/cross-field-AND-queries-with-field-boosting-tp21661099p21703051.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com
--
View this message in context:
http://www.nabble.com/cross-field-AND-queries-with-field-boosting-tp21661099p21703051.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: java
Hi,
We have documents with multiple fields conceptually, and a document is
considered a match if each of the terms in the query is in any one of the
fields(i.e a 'cross-field' AND). A simple way to do this would be to dump
all of these conceptual fields into one lucene field and do the query
Hi,
I am playing with MemoryIndex for a situation in which I have a large
number of small, ephemeral documents that I need to fire queries
at. It
appears to be at least 5x faster than RAMDirectory for my usage, which
is large enough to be interesting.
However MemoryIndex does not seem to
Hi,
I am playing with MemoryIndex for a situation in which I have a large
number of small, ephemeral documents that I need to fire queries at. It
appears to be at least 5x faster than RAMDirectory for my usage, which
is large enough to be interesting.
However MemoryIndex does not seem to
Subject
Re: Field Boosting
Please respond to
[EMAIL PROTECTED
On 19 Nov 2005, at 07:49, [EMAIL PROTECTED] wrote:
Can the boosting be greater than 2.0? For example,
field.setBoost((float)20.0).
Yes, of course. Again, have a look at the Explanation (from
IndexSearcher.explain()) to see what effect these things have on your
scores.
Erik
11/17/2005 08:46 cc
AM
Subject
Re: Field Boosting
When I boost fields while indexing, the fields still have a boost of 1.0
during searching. When I view the values via Luke, it confirms the value
of 1.0. Do I have to boost it agin during search? I want certain fields
to have higher priority/score during search. How do I get it to work? I'm
Hi Daniel,
I faced the same problem a couple of days ago. I was trying to set the
boost values while indexing, but the
results wasn't the expected. I've solved just putting the boost values
in the search query, using the '^'
operator. There is an example:
((+text:house)^25.0)
Daniel,
Could you give us a test case that shows the boost not working properly?
I'm using document level boosting (which is really what field level
boosting does under the covers) in some of my applications and it is
working as expected.
Erik
On 17 Nov 2005, at 05:39, [EMAIL
[EMAIL PROTECTED] escribió: -
Para: java-user@lucene.apache.org
De: Erik Hatcher [EMAIL PROTECTED]
Fecha: 17/11/2005 14:46
Asunto: Re: Field Boosting
Daniel,
Could you give us a test case that shows the boost not working properly?
I'm using document level boosting (which is really what
used in scoring.
Erik
Regards,
Daniel
-Erik Hatcher [EMAIL PROTECTED] escribió: -
Para: java-user@lucene.apache.org
De: Erik Hatcher [EMAIL PROTECTED]
Fecha: 17/11/2005 14:46
Asunto: Re: Field Boosting
Daniel,
Could you give us a test case that shows the boost not working
: I don't believe, though haven't checked, that doc.getBoost() is a
: valid thing to call on documents retrieved from an index. The boost
: factor gets collapsed into other factors computed at index time, so
: it is incorrect to expect the exact boost factor set at indexing time
: is available
Right. getBoost() is meaningless on retrieved documents (it isn't set
when a doc is read from the index).
There really should have been a separate class for documents retrieved
from an index vs documents added... but that's water way under the
bridge.
-Yonik
On 11/17/05, Erik Hatcher [EMAIL
This would be a good candidate for an IllegalStateException to be
thrown if the user calls this method when it's not valid. Save the
user some hassles? (one can JavaDoc to one is blue in the face, but
throwing a good RuntimeException with a message trains the users much
quicker... :) )
16 matches
Mail list logo
