If I set the boost=0 at query time and the query contains only terms with
boost=0, the scores are NaN (because weight.queryNorm = 1/0 = infinity),
instead of 0.
Peter
On Sun, Mar 1, 2009 at 9:27 PM, Erick Erickson wrote:
> FWIW, Hossman pointed out that the difference between index and
> query
FWIW, Hossman pointed out that the difference between index and
query time boosts is that index time boosts on title, for instance,
express "I care about this document's title more than other documents'
titles [when it matches]" Query time boosts express "I care about matches
on the title field mor
As suggested, I added a query-time boost of 0.0f to the 'literals' field
(with index-time boost still there) and I did get the same scores for both
queries :) (there is a subtlety between index-time and query-time boosting
that I missed.)
I also tried disabling the coord factor, but that had no a
On Sat, Feb 28, 2009 at 3:02 PM, Peter Keegan wrote:
>> in situations where you deal with simple query types, and matching query
> structures, the queryNorm
>> *can* be used to make scores semi-comparable.
>
> Hmm. My example used matching query structures. The only difference was a
> single term
> in situations where you deal with simple query types, and matching query
structures, the queryNorm
> *can* be used to make scores semi-comparable.
Hmm. My example used matching query structures. The only difference was a
single term in a field with zero weight that didn't exist in the matching
: I guess I don't really understand this comment in the similarity java doc
: then:
:
:
http://lucene.apache.org/java/2_4_0/api/org/apache/lucene/search/Similarity.html#formula_queryNorm
:
: *queryNorm(q) * is a normalizing factor used to make scores between queries
: comparable.
that comment
I guess I don't really understand this comment in the similarity java doc
then:
http://lucene.apache.org/java/2_4_0/api/org/apache/lucene/search/Similarity.html#formula_queryNorm
*queryNorm(q) * is a normalizing factor used to make scores between queries
comparable.
:/.
M
On Fri, Feb 27, 2009
Got it. This is another example of why scores can't be compared between
(even similar) queries.
(we don't)
Thanks.
On Fri, Feb 27, 2009 at 11:39 AM, Yonik Seeley
wrote:
> On Fri, Feb 27, 2009 at 9:15 AM, Peter Keegan
> wrote:
> > Any comments about this? Is this just the way queryNorm works or
On Fri, Feb 27, 2009 at 9:15 AM, Peter Keegan wrote:
> Any comments about this? Is this just the way queryNorm works or is this a
> bug?
That's just the way it works... since it's applied to all clauses, it
really just changes the range of scores returned, not relative
ordering of documents or an
Any comments about this? Is this just the way queryNorm works or is this a
bug?
Thanks,
Peter
On Fri, Feb 20, 2009 at 4:03 PM, Peter Keegan wrote:
>
> The explanation of scores from the same document returned from 2 similar
> queries differ in an unexpected way. There are 2 fields involved, 'con
The explanation of scores from the same document returned from 2 similar
queries differ in an unexpected way. There are 2 fields involved, 'contents'
and 'literals'. The 'literals' field has setBoost = 0. As you an see from
the explanations below, the total weight of the matching terms from the
'li
11 matches
Mail list logo
