Hi,-
i saw this in the Field class docs and i am figuring out the following
note in the docs:
setBoost(float boost)
Deprecated.
Index-time boosts are deprecated, please index index-time scoring
factors into a doc value field and combine them with the score at query
time using eg. FunctionSco
It looks like index-time boosting (field) is not possible since Lucene
version 7.7.2 and
i was using before for another case the BoostQuery at search time for
boosting and
this seems to be the only boosting option now in Lucene.
Best regards
On 10/18/19 10:01 AM, baris.ka...@oracle.com wro
Hi,
that's not true. You can do index time boosting, but you need to do that using
a separate field. You just index a numeric docvalues field (which may contain a
long or float value per document). Later you wrap your query with some
FunctionScoreQuery (e.g., use the Javascript function query s
Uwe,-
Thanks very much for the reply.
Is there a working example for this? Is this mentioned in the Lucene
Javadocs or any other docs so that i can look it?
this methodology seems sort of like discouraging using index time boosting.
Previous setBoost method call was fine and easy to use.
D
Hi,
> Is there a working example for this? Is this mentioned in the Lucene
> Javadocs or any other docs so that i can look it?
To index the docvalues, see NumericDocValuesField (it can be added to documents
like indexed or stored fields). You may have used them for sorting already.
> this metho
Uwe,-
Thanks, if possible i am looking for a pure Java methodology to do the
index time boosting.
This example looks like a search time boosting example:
https://urldefense.proofpoint.com/v2/url?u=https-3A__lucene.apache.org_core_7-5F7-5F2_expressions_org_apache_lucene_expressions_Expression
Sorry I was imprecise. It's a mix of both. The factors are stored per document
in index (this is why I called it index time). During query time the expression
use the index time values to fold them into the query boost at query time.
What's your problem with that approach?
Uwe
Am October 18, 2
Uwe,-
Two questions there:
i guess this is applicable to TextField, too.
And i was expecting a index writer object in the example for index time
boosting.
Best regards
On 10/18/19 2:57 PM, Uwe Schindler wrote:
Sorry I was imprecise. It's a mix of both. The factors are stored per document
Hi,
Read my original email! The index time values are written using
NumericDocValuesField. The expressions docs also refer to that when the
bindings are documented.
It's separate from the indexed data (TextField). Think of it like an additional
numeric field in your database table with a facto
Uwe,-
can this
https://lucene.apache.org/core/7_7_2/expressions/org/apache/lucene/expressions/Expression.html
doc example that You also gave be extended with NumericDocValuesField
part that needs to be done at indexing time boosting, too?
i see now why You meant that this is mixed type of b
Hi All,
I am working on implementing of an in place reindex using Lucene. In my
case, I have BSON document stored in a binary field and have a set of rules
that pull fields out of the BSON and indexes them into different Lucene
fields with different analyzers. I would like to be able to change t
11 matches
Mail list logo
