[
https://issues.apache.org/jira/browse/OAK-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901109#comment-15901109
]
Vikas Saurabh commented on OAK-5899:
------------------------------------
[~tmueller], I was recently trying to read up the index structure a bit to get
some handle on OAK-5707. Admittedly, I don't know much of lucene's low-level
APIs and there might be a better way(s) to do it. It seems to me that we should
be able to get a histogram of num-doc-per-term-per-field in lucene too. That
said, I feel that we should set
selectivity/weight/whatever-name-we-come-up-with when standard-dev of
num-doc-per-term-per-field is relatively low (and yes, both "when" and
"relatively" need to qualified better)
> PropertyDefinitions should allow for some tweakability to declare usefulness
> ----------------------------------------------------------------------------
>
> Key: OAK-5899
> URL: https://issues.apache.org/jira/browse/OAK-5899
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Vikas Saurabh
> Priority: Minor
> Fix For: 1.8
>
>
> At times, we have property definitions which are added to support for dense
> results right out of the index (e.g. {{contains(\*, 'foo') AND
> \[bar]='baz'}}).
> In such cases, the added property definition "might" not be the best one to
> answer queries which only have the property restriction (eg only
> {{\[bar]='baz'}}
> There should be a way for property definition to declare this. May be there
> are cases of some spectrum too - i.e. not only a boolean-usable-or-not, but
> some kind of scale of how-usable is it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
