[
https://issues.apache.org/jira/browse/LUCENE-8769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16866797#comment-16866797
]
Atri Sharma commented on LUCENE-8769:
-------------------------------------
I think we would still need a way to process NOT ranges (for NOT (a, b), we
could rewrite to (-infinity, a), (b, infinity)?)
I agree, OR should be supported. The subtle catch there is that OR would
normally be across multiple ranges, not single ranges. EG: (A AND B) OR (C AND
D NOT E). How do we flatten that to a single MultiRangeQuery? The other option
is to convert it into two MultiRangeQueries, execute both and then OR their
result (of course, short circuit if the first one evaluates to true). This can
be done for AND across clauses as well.
I am happy to put it in sandbox first, and then eventually move it to core? is
there a criteria model that we follow for that transition?
> Range Query Type With Logically Connected Ranges
> ------------------------------------------------
>
> Key: LUCENE-8769
> URL: https://issues.apache.org/jira/browse/LUCENE-8769
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Atri Sharma
> Priority: Major
> Attachments: LUCENE-8769.patch, LUCENE-8769.patch, LUCENE-8769.patch
>
>
> Today, we visit BKD tree for each range specified for PointRangeQuery. It
> would be good to have a range query type which can take multiple ranges
> logically ANDed or ORed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
