Jon Marius Venstad

```java boolean closed = true; new MultiRangeItem("my_range", closed).addRange(3, 5).addRange(4, 8)... // range type in document, if we add this new MultiRangeItem("my_start", "my_end", ! closed).addRange(1, 2)... // pair of fields is...

To summarise today's discussion: 1. We would like a dedicated Java API, like the one suggested here, which allows more assumptions on the query term: 1. we can collapse overlapping...

Pondered a bit. The reverse index, in its simplest form, can just be two sorted arrays `A`, `B`, containing the range endpoints. Looking up whether a document range `(x, y)`...

We need something more than that to express ranges in the query against ranges in the document in a clean way. Either a new field type, or range items that...

Clarification: the proposed API is OK, but serialisation should be more general.

So the serialisation format needs to hold 1. operation type (`AND`, `OR` for now) 2. number of terms (positive integer) 3. term blueprint for translating each following term to something...

Nice. Unrelated test failure.

Need to prune e.g., (1, 1), when [0, 1) is already present. That isn't handled now, as these two do not overlap.

PTAL.

#31255