mirror of https://github.com/apache/lucene.git
Move LUCENE-10614 CHANGES entry to 10.0 and add MIGRATE entry
This commit is contained in:
parent
5ef7e5025d
commit
d6dbe4374a
|
@ -48,6 +48,8 @@ Improvements
|
|||
* LUCENE-10216: Use MergePolicy to define and MergeScheduler to trigger the reader merges
|
||||
required by addIndexes(CodecReader[]) API. (Vigya Sharma, Michael McCandless)
|
||||
|
||||
* LUCENE-10614: Properly support getTopChildren in RangeFacetCounts. (Yuting Gan)
|
||||
|
||||
Optimizations
|
||||
---------------------
|
||||
(No changes)
|
||||
|
@ -109,8 +111,6 @@ Improvements
|
|||
|
||||
* GITHUB#983: AbstractSortedSetDocValueFacetCounts internal code cleanup/refactoring. (Greg Miller)
|
||||
|
||||
* LUCENE-10614: Properly support getTopChildren in RangeFacetCounts. (Yuting Gan)
|
||||
|
||||
Optimizations
|
||||
---------------------
|
||||
* LUCENE-8519: MultiDocValues.getNormValues should not call getMergedFieldInfos (Rushabh Shah)
|
||||
|
|
|
@ -40,6 +40,13 @@ with the new one during object instantiation.
|
|||
Except for a few exceptions, almost all normalizer and stemmer classes are now package private. If your code depends on
|
||||
constants defined in them, copy the constant values and re-define them in your code.
|
||||
|
||||
### LongRangeFacetCounts / DoubleRangeFacetCounts #getTopChildren behavior change (LUCENE-10614)
|
||||
|
||||
The behavior of `LongRangeFacetCounts`/`DoubleRangeFacetCounts` `#getTopChildren` actually returns
|
||||
the top-n ranges ordered by count from 10.0 onwards (as described in the `Facets` API) instead
|
||||
of returning all ranges ordered by constructor-specified range order. The pre-existing behavior in
|
||||
9.x and earlier can be retained by migrating to the new `Facets#getAllChildren` API (LUCENE-10550).
|
||||
|
||||
## Migration from Lucene 9.0 to Lucene 9.1
|
||||
|
||||
### Test framework package migration and module (LUCENE-10301)
|
||||
|
|
Loading…
Reference in New Issue