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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2013/12/05 09:01:43 UTC
[jira] [Resolved] (OAK-913) Query: relative fulltext conditions
return the wrong result
[ https://issues.apache.org/jira/browse/OAK-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller resolved OAK-913.
--------------------------------
Resolution: Fixed
It looks like this particular case was fixed quite a long time ago.
> Query: relative fulltext conditions return the wrong result
> -----------------------------------------------------------
>
> Key: OAK-913
> URL: https://issues.apache.org/jira/browse/OAK-913
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 0.13
>
>
> Fulltext conditions of the following form return the child node instead of the parent node:
> {code}
> contains([node1/text], 'hello')
> {code}
> This is because the filter doesn't contain the relative path (it doesn't contain the property name either, but that's not the problem here).
> The problem here is not the Lucene index, but the filter API, so it can't be easily fixed. I think it makes sense to fix it as part of OAK-902.
--
This message was sent by Atlassian JIRA
(v6.1#6144)