[
https://issues.apache.org/jira/browse/OAK-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller resolved OAK-2357.
---------------------------------
Resolution: Won't Fix
We decided to not fix this issue. Instead, the "new" Lucene full-text index
should be used that aggregates at index time (rather than at query time), if
this feature is needed.
The "old" Lucene full-text index is still needed in case the added security is
needed (which is not possible with the "new" Lucene index).
> Aggregate index: Abnormal behavior of "and not(..)" clause in XPath
> -------------------------------------------------------------------
>
> Key: OAK-2357
> URL: https://issues.apache.org/jira/browse/OAK-2357
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Affects Versions: 1.0.8, 1.1.3
> Reporter: Geoffroy Schneck
> Assignee: Thomas Mueller
> Priority: Minor
> Fix For: 1.0.13, 1.2
>
>
> Create a node {{/tmp/node1}} with property {{prop1 = 'foobar'}}.
> Perform following query :
> {noformat}
> /jcr:root/tmp//*[prop1 = 'foobar' and not(prop1 = 'foobarrrr')]
> {noformat}
> {{/tmp/node1}} is returned by the search.
> Now replace the = clause by the {{jcr:contains()}} :
> {noformat}
> /jcr:root/tmp//*[jcr:contains(., 'foobar') and not(jcr:contains(.,
> 'foobarrrrr'))]
> {noformat}
> No result is returned.
> Despite the presence of {{/tmp/node1}} in the results of
> {{/jcr:root/tmp//\*\[not(jcr:contains(., 'foobarrrrr'))\]}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
