: Adrien Grand
Sent: Wednesday, March 23, 2022 17:58
To: Lucene Users Mailing List
Subject: Re: Re: Custom scores and sort
CAUTION: external mail
Sorry Claude, but I have some trouble following what you are doing
with your CustomScoreQuery. It feels like your query is doing
something that breaks some
Sorry Claude, but I have some trouble following what you are doing
with your CustomScoreQuery. It feels like your query is doing
something that breaks some assumptions that Lucene makes.
Have you looked at existing ways that Lucene supports boosting
documents by recency, such as putting a LongDist
Adrien, thank you for your answer and sorry for the lack of clarity.
No, the score of a document does not depend on the score of another
document, the problem lies within a document.
There are several "only once score" fields; to simplify, I suppose there is
only one "only once score" field;
a do
It's a bit hard for me to parse what you are trying to do, but it
looks like you are making assumptions about how Lucene works
internally that are not correct.
Do I understand correctly that your scoring mechanism has dependencies
on other documents, ie. the score of a document could depend on the
Hi!
I see where the problem lies but I can't find a way to solve it.
First feature: one of the fields must be scored only once: if a document
matches this field several times (the values are different), the score is
counted only the first time.
A map is given as an argument to the CustomScoreQuer
Hello Claude,
here is what I'm doing and it seems to work, I haven't yet created
failure tests. Maybe more expert member will have more information.
Date field inserted:
final Date parse = DATE_FORMAT.parse(DATE_FORMAT.format(o1));
new LongPoint(attributeName, parse.getTime()));
The sorter:
Sor
