jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2114) Aggregate index returns the ancestor node as well
Date Tue, 01 Nov 2016 15:26:58 GMT

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

Thomas Mueller commented on OAK-2114:
-------------------------------------

The known workaround is to use a "compatVersion=2" lucene index. That is, not an aggregate
index.

Still, it would be nice if this is fixed, because the aggregate index does more security checks
than the compatVersion 2 index.

> 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: Davide Giannella
>             Fix For: 1.6
>
>         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.4#6332)

Mime
View raw message