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

Thomas Mueller commented on OAK-4637:
-------------------------------------

Even more general would be to use an expression, similar to how function-based 
indexes work. So you could add a condition "[@productType='shoe' and @size <= 
30]" for an index "kid-shoes" that would only index small shoes. The indexed 
property could be (for example) "color". Such an index would be used for 
queries with the condition "[@productType = 'shoe' and @size <= 30 and @color = 
'green']". Sure, it's probably more than what is needed in most cases, but we 
could re-use the function-based index processing we already have in oak-lucene 
(probably move it to oak-core).

> Property index: include/exclude pattern list
> --------------------------------------------
>
>                 Key: OAK-4637
>                 URL: https://issues.apache.org/jira/browse/OAK-4637
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.6
>
>
> 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.4#6332)

Reply via email to