[
https://issues.apache.org/jira/browse/OAK-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740562#comment-14740562
]
Davide Giannella commented on OAK-3371:
---------------------------------------
[~tmueller], [~chetanm] there's an edge case in case of lucene
aggregate v1.
If you specify an aggregation rule, let's say
{{\[nt:folder]/\[subnode]}} and then you perform a query like
{{from \[nt:folder] where not contains(foo, 'bar')}}; a node like
{noformat}
{{ test { jcr:primaryType = nt:folder, foo = bar, subnode : { ... } } }}
{noformat}
where {{subnode}} does not have the {{foo}} property or it's not set
to {{bar}}, will be returned anyhow as of the aggregation rule. I
personally don't consider this an issue, rather an expected behaviour.
Thoughts?
> 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-2.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)
