You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/03/27 05:01:41 UTC
[jira] [Commented] (OAK-2114) Aggregate index returns the ancestor
node as well
[ https://issues.apache.org/jira/browse/OAK-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942650#comment-15942650 ]
Chetan Mehrotra commented on OAK-2114:
--------------------------------------
[~edivad] Given aggregate index is not used I would suggest to resolve this issue as Wont Fix
> Aggregate index returns the ancestor node as well
> -------------------------------------------------
>
> Key: OAK-2114
> URL: https://issues.apache.org/jira/browse/OAK-2114
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, lucene, query
> Affects Versions: 1.1.0
> Reporter: Davide Giannella
> Assignee: Thomas Mueller
> Fix For: 1.8
>
> Attachments: OAK-2114-test.patch
>
>
> When performing a query like
> {noformat}
> //*[jcr:contains(. 'something') or jcr:contains(metadata, 'something')]
> {noformat}
> having a structure like {{/content/node/jcr:content}} where {{jcr:content}} contains 'something' both {{/content/node}} and {{/content/node/jcr:content}} are returned.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)