[
https://issues.apache.org/jira/browse/OAK-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-3352:
-------------------------------
Attachment: OAK-3352.patch
Attaching [patch|^OAK-3352.patch]. The patch parses query same as
{{rep:excerpt()}} does (i.e. simple String.contains() in filter) - I'm not sure
if this is fine or we should put it in as a flag in filter as Chetan suggested
in his proposal.
Column name used is oak:explainScore although I think something of the form
oak:explainScore*()* might be better (parentheses to give better sense that
this is not a property name).
In absence of a better idea, the test case just checks if results contains
{{(MATCH)}} as a couple of explanations that I saw had this string in the
explanation.
BTW,
[IndexSearcher.explain|https://lucene.apache.org/core/4_6_0/core/org/apache/lucene/search/IndexSearcher.html#explain%28org.apache.lucene.search.Query,%20int%29]
suggests that calculating score can be slow for performance - so, we should
specify it clearly in documentation too.
[~chetanm], [~teofili], can you please review it?
> Expose Lucene search score explanation
> ---------------------------------------
>
> Key: OAK-3352
> URL: https://issues.apache.org/jira/browse/OAK-3352
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: lucene, query
> Reporter: Chetan Mehrotra
> Fix For: 1.4
>
> Attachments: OAK-3352.patch
>
>
> Lucene provides {{Explanation}} [1] support to understand how the score for a
> particular search result is determined. To enable users to reason out about
> fulltext search results in Oak we should expose this information as part of
> query result
> [1]
> https://lucene.apache.org/core/4_0_0/core/org/apache/lucene/search/Explanation.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
