You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/07/06 11:04:00 UTC
[jira] [Updated] (OAK-5899) PropertyDefinitions should allow for
some tweakability to declare usefulness
[ https://issues.apache.org/jira/browse/OAK-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra updated OAK-5899:
---------------------------------
Attachment: OAK-5899-v1.patch
[patch|^OAK-5899-v1.patch] for the same.
This changes the IndexPlanner such that If any property definition has weight == 0 then that property would not be counted for indexed props. However that property would still be used in query execution
[~tmueller] Please review
> 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
> Assignee: Thomas Mueller
> Priority: Critical
> Fix For: 1.8, 1.6.3
>
> Attachments: OAK-5899-v1.patch
>
>
> 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.4.14#64029)