[
https://issues.apache.org/jira/browse/OAK-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998345#comment-15998345
]
Thomas Mueller commented on OAK-4637:
-------------------------------------
Yes that's true, for "not null" the index is not used if it has an pattern.
> {{/jcr:root/etc/replication//\*\[jcr:like(@sling:resourceType,
> "cq/replication/components/%agent")\]}}
I will try to find a way to make this work.
> 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)
