[
https://issues.apache.org/jira/browse/OAK-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760305#comment-17760305
]
Julian Reschke edited comment on OAK-8711 at 8/30/23 10:42 AM:
---------------------------------------------------------------
trunk: (1.26.0)
[98652c0008|https://github.com/apache/jackrabbit-oak/commit/98652c0008c771cd33d0b8d153f5bef397b70551]
1.22:
[c842b6bc25|https://github.com/apache/jackrabbit-oak/commit/c842b6bc256578ac70a7ee148ad36cddf8bda9dc]
was (Author: reschke):
trunk: (1.26.0)
[98652c0008|https://github.com/apache/jackrabbit-oak/commit/98652c0008c771cd33d0b8d153f5bef397b70551]
> Queries with facets should not use traversal
> --------------------------------------------
>
> Key: OAK-8711
> URL: https://issues.apache.org/jira/browse/OAK-8711
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, lucene
> Reporter: Nitin Gupta
> Assignee: Nitin Gupta
> Priority: Major
> Labels: amrit
> Fix For: 1.24.0, 1.22.17
>
> Attachments: OAK-8711.patch
>
>
> Consider a scenario where a query is there with facets and the traversal cost
> is less than the index cost that serves the facet query . This would be
> problematic.
>
> In this case we should maybe set the traversal cost to infinity so that
> traversal is not an option for queries with facets.
>
> In case there is no index available to serve this faceted query we can
> probably throw an exception with a meaningful message .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
