jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-5899) PropertyDefinitions should allow for some tweakability to declare usefulness
Date Tue, 07 Mar 2017 13:10:38 GMT

    [ https://issues.apache.org/jira/browse/OAK-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899399#comment-15899399
] 

Thomas Mueller commented on OAK-5899:
-------------------------------------

Lucene supports field info, and the Lucene index JMX bean allows to read that info using getFieldInfo,
see OAK-3219. This is a start. I added that to the JMX bean so that we can find out how fast
it is. It could be the basis for an "analyze" tool for Oak.

> 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)

Mime
View raw message