[
https://issues.apache.org/jira/browse/OAK-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035244#comment-15035244
]
Chetan Mehrotra commented on OAK-3352:
--------------------------------------
bq. + boolean addExplain = queryStatement != null &&
queryStatement.contains(QueryImpl.OAK_EXPLAIN_SCORE);
I would prefer to add this to the filter as similar construct can be used for
other indexes also [~tmueller] Thoughts? How the explanation requirement is
expressed is implementation detail of query and index implementation need not
analyze the query statement to infer this.
bq. 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).
So instead of sounding like function lets change the name to
{{oak:scoreExplanation}} ?
bq. BTW, IndexSearcher.explain suggests that calculating score can be slow for
performance - so, we should specify it clearly in documentation too.
As the cost is only involved if this feature is made use of in query I think it
should be fine. But yes as part of document update regarding this feature it
can be highlighted
> 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)
