[
https://issues.apache.org/jira/browse/OAK-7897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh resolved OAK-7897.
--------------------------------
Resolution: Won't Fix
Considering what [~tmueller] mentioned and that the cases where OR can
translate to IN, cost of IN is expected to be lower anyway - closing this issue
as won't fix.
> Queries with OR simplified to IN shouldn't have alternative UNION query
> -----------------------------------------------------------------------
>
> Key: OAK-7897
> URL: https://issues.apache.org/jira/browse/OAK-7897
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Thomas Mueller
> Priority: Minor
>
> Queries like {noformat} SELECT [rep:facet(text)] FROM [nt:base] WHERE [name]
> = 'Node1' OR [name] = 'Node2' {noformat} which would get simplified to {{IN}}
> clause still weigh in cost of alternative query with {{UNION}}. We should
> avoid that.
> /cc [~tmueller]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
