[
https://issues.apache.org/jira/browse/OAK-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733373#comment-14733373
]
Vikas Saurabh commented on OAK-3352:
------------------------------------
To me this seems like a debug feature (unless I'm missing the intent). So,
maybe it'd make more sense to have property (from debug/inspection pov) on
index def. Then we can use the value of this property to log explanation of
rows. I feel exposing it to rows kind of implies an api contract - and I'm not
sure if how we'd like to maintain/extend/modify 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
>
>
> 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)
