lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Grand (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8477) Improve handling of inner disjunctions in intervals
Date Mon, 03 Sep 2018 13:54:01 GMT


Adrien Grand commented on LUCENE-8477:

I'd be tempted to just document this behavior for now. I'm afraid that introducing non-minimized
intervals will introduce similar corner-cases to what we have with spans and sloppy phrase

Rewriting automatically feels a bit wrong given that we would be replacing an IntervalsSource
with another IntervalsSource that has different matches. However this is something that could
be implemented on top of intervals in query parsers by having an intermediate representation
of IntervalsSources and push disjunctions to the top?

> Improve handling of inner disjunctions in intervals
> ---------------------------------------------------
>                 Key: LUCENE-8477
>                 URL:
>             Project: Lucene - Core
>          Issue Type: New Feature
>            Reporter: Alan Woodward
>            Priority: Major
> The current implementation of the disjunction interval produced by {{Intervals.or}} is
a direct implementation of the OR operator from the Vigna paper.  This produces minimal intervals,
meaning that (a) is preferred over (a b), and (b) also over (a b).  This has advantages when
it comes to counting intervals for scoring, but also has drawbacks when it comes to matching. 
For example, a phrase query for ((a OR (a b)) BLOCK (c)) will not match the document (a b
c), because (a) will be preferred over (a b), and (a c) does not match.
> This ticket is to discuss the best way of dealing with disjunctions.

This message was sent by Atlassian JIRA

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

View raw message