lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (LUCENE-1260) Norm codec strategy in Similarity
Date Thu, 10 Apr 2008 00:16:06 GMT


Hoss Man commented on LUCENE-1260:

bq. My use case is really about document boost and not normalization.

bq. So another solution to this is to introduce a (variable bit sized?) document boost file
and completely separate it from the norms instead...

1) "norms" is a vague term.  currently "lengthNorm" is folded in with "field boosts" and "doc
boosts" to form a generic "fieldNorm" ... I assumed you were interested in a more general
way to improve the resolution of "fieldNorm"

2) your description of general purpose variable sized document boosting sounds exactly like
LUCENE-1231 ... in the long run utilities using LUCENE-1231 (or something like it) to replace
"field boosts" and "length norms" might make the most sense as a way to eliminate the current
static Norm encoding and put more flexibility in the hands of users

> Norm codec strategy in Similarity
> ---------------------------------
>                 Key: LUCENE-1260
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>    Affects Versions: 2.3.1
>            Reporter: Karl Wettin
>         Attachments: LUCENE-1260.txt
> The static span and resolution of the 8 bit norms codec might not fit with all applications.

> My use case requires that 100f-250f is discretized in 60 bags instead of the default..

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message