[
https://issues.apache.org/jira/browse/OAK-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049010#comment-16049010
]
Thomas Mueller commented on OAK-4637:
-------------------------------------
http://svn.apache.org/r1798661 (trunk)
Now the following properties are supported: "valueExcludedPrefixes",
"valueIncludedPrefixes", and "valuePattern". Excluded and included are
multi-value String properties (even thought if there is just one entry, you can
also use a simple string). They are prefixes prefix of the string value, so
that you can filter the prefix "slingevent:Job", or only include
"cq/replication", and so on. This works with "like" conditions of the form
{{/jcr:root/etc/replication//*[jcr:like(@sling:resourceType,
"cq/replication/components/%agent")]}}.
Now it needs to be tested if this solves the original problem. Documentation is
missing as well.
> Property index: include/exclude key pattern list
> ------------------------------------------------
>
> Key: OAK-4637
> URL: https://issues.apache.org/jira/browse/OAK-4637
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: property-index
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Critical
> Fix For: 1.8
>
>
> In some cases, property indexes contain many nodes, and updating them can be
> slow. Right now we have filters for node and mixin types, path (include and
> exclude).
> An include and exclude list of values (patterns) would be useful. For example
> the property "status", if we only ever run queries with the condition "status
> = 'ACTIVE'", then nodes with status INACTIVE and DONE don't need to be
> indexed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
