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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2017/10/01 04:06:00 UTC
[jira] [Updated] (OAK-6750) Lucene facets don't work with relative
properties
[ https://issues.apache.org/jira/browse/OAK-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vikas Saurabh updated OAK-6750:
-------------------------------
Attachment: OAK-6750-testCase.patch
[^OAK-6750-testCase.patch] has a test case that fails. (Can't commit as Junit3 doesn't seem to have @Ignore :-/).
> Lucene facets don't work with relative properties
> -------------------------------------------------
>
> Key: OAK-6750
> URL: https://issues.apache.org/jira/browse/OAK-6750
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Fix For: 1.8
>
> Attachments: OAK-6750-testCase.patch
>
>
> Facets currently work only when faceted dimension is direct property of selected node e.g. {{select \[jcr:path], \[rep:facet(jc/text)] from \[nt:base] where ... }} doesn't work but {{select \[jcr:path], \[rep:facet(text)] from \[nt:base] where ... }} works (assume correct index defs).
> The issue is that {{ast/SelectorImpl#currentOakProperty}} check if {{rep:facet(jc/text)}} is a relative path or not and incorrectly 'feels' that it indeed is - it then proceeds ahead to traverse down a tree with elements {{rep:facet(jc, text)}} which makes no sense.
> /cc [~teofili], [~tmueller]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)