[
https://issues.apache.org/jira/browse/OAK-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998401#comment-15998401
]
Thomas Mueller commented on OAK-4637:
-------------------------------------
This becomes a range condition:
{{property=\[sling:resourceType=\[\[cq/replication/components/..,
..cq/replication/components0\]\]]}}. It is possible to use a "like" condition
as well (in addition to the range condition for example).
It's hard to check whether a regular expression is a subset / superset of
another regular expression in _general_. So probably it's easier to support
"exclude", then parse the regular expression in Oak (just supporting a limited
subset of expressions) and check whether the like condition can possibly match.
> 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.3.15#6346)
