diff options
| author | jonmv <venstad@gmail.com> | 2022-10-13 14:19:16 +0200 |
|---|---|---|
| committer | jonmv <venstad@gmail.com> | 2022-10-26 12:07:17 +0200 |
| commit | a845add7c80c437d410a91da28dff6357304e748 (patch) | |
| tree | 2ae0cff49b93eed174bb7b57a1ac583986413479 /container-search/src/main/java/com/yahoo/prelude | |
| parent | d92c5a98abe7f05efed896a93d47695ea76215f3 (diff) | |
Rebase, change to JUnit5, update ABI spec
Diffstat (limited to 'container-search/src/main/java/com/yahoo/prelude')
| -rw-r--r-- | container-search/src/main/java/com/yahoo/prelude/query/MultiRangeItem.java | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/container-search/src/main/java/com/yahoo/prelude/query/MultiRangeItem.java b/container-search/src/main/java/com/yahoo/prelude/query/MultiRangeItem.java index 24d4623b2b8..27696b85da3 100644 --- a/container-search/src/main/java/com/yahoo/prelude/query/MultiRangeItem.java +++ b/container-search/src/main/java/com/yahoo/prelude/query/MultiRangeItem.java @@ -39,7 +39,7 @@ import static java.util.Objects.requireNonNull; * possible to achieve any matching by choosing inclusiveness for the query ranges properly. * For the case where document ranges are to be treated as exclusive, and the query has single points, this * becomes weird, since the ranges [1, 1), (1, 1] and (1, 1) are all logically empty, but this still works :) - * + * <p> * Unless ranges are added in ascending start order, the implementation lazily sorts and merges ranges, * when a representation of the item is required. This is typically when the query is serialized and sent * to the backend, or when trace information is written, or {@link #toString()} is called on the item. |