You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2016/11/22 13:12:59 UTC
[jira] [Created] (OAK-5143) Augmented query terms due to
FulltextQueryTermsProvider tend to get more weight while scoring results
Vikas Saurabh created OAK-5143:
----------------------------------
Summary: Augmented query terms due to FulltextQueryTermsProvider tend to get more weight while scoring results
Key: OAK-5143
URL: https://issues.apache.org/jira/browse/OAK-5143
Project: Jackrabbit Oak
Issue Type: Improvement
Components: lucene
Affects Versions: 1.4
Reporter: Vikas Saurabh
Assignee: Vikas Saurabh
Priority: Minor
Fix For: 1.8
Current implementation of using FulltextQueryTermsProvider service(s) collects query terms from these objects and attaches it to full text query as a big or clause. So, if original query was {{a='b' OR c='d'}} and we had a query term provider which would add {{e='f'}} then the final query would look like {{(a='b' OR c='d') OR e='f'}}. This query is correct semantically but while scoring from lucene's perspective the clause {{e='f'}} can singly allow the condition to be true and hence it gets more weight (actually, the truth is that the first part get less weight if only one condition from first part is met - ie if indeed a='b' but c!='d' then the score for first part of the query get a multiplier of 0.5 aka coord-factor \[0]).
\[0]: https://lucene.apache.org/core/4_7_0/core/org/apache/lucene/search/similarities/TFIDFSimilarity.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)