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 2019/01/09 10:07:00 UTC
[jira] [Commented] (OAK-7975) Facet extraction fails while
requesting multiple facets and one of the requested facets doesn't have
indexed values
[ https://issues.apache.org/jira/browse/OAK-7975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738059#comment-16738059 ]
Vikas Saurabh commented on OAK-7975:
------------------------------------
Backported to 1.8 at [r1850838|https://svn.apache.org/r1850838] and to 1.6 at [r1850840|https://svn.apache.org/r1850840].
> Facet extraction fails while requesting multiple facets and one of the requested facets doesn't have indexed values
> -------------------------------------------------------------------------------------------------------------------
>
> Key: OAK-7975
> URL: https://issues.apache.org/jira/browse/OAK-7975
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Major
> Fix For: 1.10, 1.9.14
>
>
> Consider a content like
> {noformat}
> + /test
> - foo=bar
> {noformat}
> with index def faceting multiple properties - something like
> {noformat}
> + /oak:index/foo/indexRules/nt:base/properties
> + foo
> - propertyIndex=true
> - facets = true
> + bar
> - facets = true
> {noformat}
> Then a query like
> {noformat}
> SELECT [rep:facet(foo)], [rep:facete(bar)] FROM [nt:base]
> {noformat}
> should not fail.
> Note that the failure requires requesting on multiple facets and one of them must not have any indexed value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)