[
https://issues.apache.org/jira/browse/OAK-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992520#comment-15992520
]
Thomas Mueller commented on OAK-4637:
-------------------------------------
[~chetanm] it is possible to use regular expressions to exclude entries as
well, using
[negative|http://stackoverflow.com/questions/2078915/a-regular-expression-to-exclude-a-word-string]
[look-around|http://stackoverflow.com/questions/406230/regular-expression-to-match-a-line-that-doesnt-contain-a-word].
Even thought it is probably not that efficient (I'm not sure if it's
measurably slower).
it would be good to know more exact use cases. Use cases I have in mind are:
* as a basis for OAK-4653 (include list should be sufficient here)
* to exclude certain common "slingResourceType" values (for example), and
similar, in order to shrink the index size (only index what is really queried
for).
> 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)
