[OAK-5899] PropertyDefinitions should allow for some tweakability to declare usefulness

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.7.4, 1.6.3, 1.8.0
• Component/s: lucene
• Assignee: Chetan Mehrotra
• Reporter: Vikas Saurabh
• Created: 07/Mar/17 12:18
• Updated: 08/Oct/19 15:21
• Resolved: 12/Jul/17 04:34

Description

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.

Issue Links

• relates to: OAK-5858 Lucene index may return the wrong result if path is excluded