lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atri Sharma (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8769) Range Query Type With Logically Connected Ranges
Date Tue, 18 Jun 2019 17:45:00 GMT


Atri Sharma commented on LUCENE-8769:

Thinking more about this, I think what can be done is:


1) Introduce NOT semantics by translating NOT (a, b) to (-infinity, a) AND (b, infinity)

2) Introduce a RangeClause which contains a bunch of ranges and associated AND and NOT clauses
(not OR). Each RangeClause will be independently executed, and then the final result then
ANDed or ORed. For eg:


(a AND B) OR (c NOT d) converts to two RangeClauses: \{a, b, AND}, \{c, d, NOT}, where the
RangeClauses are connected by OR, so the independent results of both clauses are then ORed
to give final result.


Does this seem useful and a doable approach?

> Range Query Type With Logically Connected Ranges
> ------------------------------------------------
>                 Key: LUCENE-8769
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message