karl wettin wrote:
My own immediate thought is to compromise by allowing boost per term in
document. Simply remove the norms-methods from the IndexReader and add
a new one to the TermEnum and fall back on the field boost. How would
the value be picked up by the scorer?
Boost per position,
26 apr 2006 kl. 19.18 skrev Doug Cutting:
karl wettin wrote:
How about refactoring fields to something like:
[Document](fieldName)<#> {0..1} ->[Field +boost]<#>
{0..*} -> [FieldValue +store +index +termVector]
If you think you have a simple, back-compatible way to do this,
pleas
karl wettin wrote:
karl wettin wrote:
This could lead me to believe I can use different boost for fields
with the same name within one document.
You can. The values are multiplied to produce the final boost value
for the field.
It's not really the same thing as I tried to describe thou
25 apr 2006 kl. 19.34 skrev Doug Cutting:
karl wettin wrote:
This could lead me to believe I can use different boost for
fields with the same name within one document.
You can. The values are multiplied to produce the final boost
value for the field. This is described in:
http://luce
karl wettin wrote:
This could lead me to believe I can use different boost for fields with
the same name within one document.
You can. The values are multiplied to produce the final boost value for
the field. This is described in:
http://lucene.apache.org/java/docs/api/org/apache/lucene/d
25 apr 2006 kl. 18.56 skrev karl wettin:
How about refactoring fields to something like:
[Document](fieldName)<#> {0..1} ->[Field +boost]<#> {0..*} -
>[FieldValue +store +index +termVector]
instead of as now:
[Document](fieldName)<#> {0..1} ->[Field +boost +store +index
+term
