[
https://issues.apache.org/jira/browse/OAK-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334548#comment-14334548
]
Thomas Mueller commented on OAK-2529:
-------------------------------------
As for the first part (use "not null" condition in the filter), it is quite
easy to do and doesn't need changes in the index implementations. I will do
that.
The second part (support and use "<> 1" in the filter), it requires more
changes. I moved that part to OAK-2547. We might not need this for the 1.0
branch.
> Index usage for "not equals" conditions
> ---------------------------------------
>
> Key: OAK-2529
> URL: https://issues.apache.org/jira/browse/OAK-2529
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 1.2, 1.0.12, 1.1.8
>
>
> Queries with "not equals" conditions don't currently use an index. Example:
> {noformat}
> /jcr:root/content//*[@contentType != 'container']
> {noformat}
> Such conditions should result in a "not null" property restrictions (so that
> property indexes can be used if available, and if there are only few entries
> for this property).
> Also, "not equal" need to be used and supported in the filter. Currently, in
> FilterImpl, this is not supported and used, and would throw a
> IllegalArgumentException if used. This is for indexes that natively support
> this feature (such as Apache Lucene and Solr).
> Also, this needs to be supported in the Lucene and Solr index.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
