[
https://issues.apache.org/jira/browse/OAK-7975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746169#comment-16746169
]
Davide Giannella commented on OAK-7975:
---------------------------------------
bq. is there some way to fix release notes for 1.6.16 itself?
while we could update the tag in svn I don't like the idea for this minor
things. Additionally it will create discrepancies between the announcements
sent along the public release and the actual release notes we'd have in tag.
I'd say that keeping both versions is a good one along with your comment.
What you could do more is to broadcast the situation on oak-dev just to make
sure that the community knows about this aspect.
> 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: Minor
> Fix For: 1.10.0, 1.6.16, 1.8.11, 1.6.17, 1.11.0
>
>
> 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)
