[
https://issues.apache.org/jira/browse/OAK-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037657#comment-15037657
]
Vikas Saurabh commented on OAK-3352:
------------------------------------
bq. I would prefer to add this to the filter as similar construct can be used
for other indexes
rep:excerpt follows the same idea of parsing the query. I'd create and issue to
have flag in query engine to parse and declare the intent that we need to
calculate excerpt or explanation.
In the mean time, we can probably commit the current patch as is (including
renaming oak:explainScore to oak:scoreExplanation) - fixing that new issue
would just be an oak internal detail and won't affect the result of queries
anyway. Does that sound ok?
> 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)
