jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3371) Wrong evaluation of NOT clause
Date Tue, 08 Sep 2015 11:02:46 GMT

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

Davide Giannella commented on OAK-3371:

Quick analysis. 

Nodetype index should not play in case of full-text queries. The
full-text condition doesn't make it to the filter, nor as {{not}} nor
as {{full-text}}.

This makes the nodetype index not aware of the full-text condition and
returns all the nodes that matches the path condition.

With OAK-2050 we removed the support of Fulltext queries from the
query engine saying that full-text queries should be played only by a
full-text index (ie: lucene or solr).

Lucene should already be able to support a single {{NOT CONTAINS()}}.

So the next steps are:

- find a way to represent {{NOT CONTAINS()}} in the Filter as a
- Nodetype index should then not play any longer
- Ensure lucene handle correctly the condition.
- Ensure Solr handle correctly the condition.

/cc [~tmueller], [~chetanm], [~teofili]

> Wrong evaluation of NOT clause
> ------------------------------
>                 Key: OAK-3371
>                 URL: https://issues.apache.org/jira/browse/OAK-3371
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: query
>    Affects Versions: 1.2.4, 1.3.5
>            Reporter: Davide Giannella
>            Assignee: Davide Giannella
>             Fix For: 1.3.6
>         Attachments: OAK-3371-test.diff
> When executing a query like 
> {noformat}
> {noformat}
> and the {{nodeType}} index plays the not clause is not applied properly. Nodes **with**
the property are returned as well.
> [test|^OAK-3371-test.diff] showing the bug.

This message was sent by Atlassian JIRA

View raw message