[
https://issues.apache.org/jira/browse/OAK-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900693#comment-14900693
]
Davide Giannella commented on OAK-3371:
---------------------------------------
By looking at
http://www.day.com/specs/jcr/2.0/6_Query.html#6.7.19%20FullTextSearch
I understand that a query in the format {{not contains (x, 'foo bar'}}
has to be translated into {{(not contains(x, 'foo') and not contains(x, bar))}}.
Read it as all the terms in the fulltext separated by white space must
be ANDed.
Will start working towards it.
Gave a look at your patch, but understanding the diff on top my diff
it's rather tricky. :)
> 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.7
>
> Attachments: OAK-3371-2.patch, OAK-3371-3-oak-core.patch,
> OAK-3371-test.diff, OAK-3371.patch
>
>
> When executing a query like
> {noformat}
> SELECT * FROM [nt:unstructured] WHERE ISDESCENDANTNODE([/test]) AND NOT
> CONTAINS(foo, 'bar')
> {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
(v6.3.4#6332)
