We allow LeafFieldComparators to only accept a docID, get the equivalent feature value(s) and compare against the bottom/top of the values set for the comparator. This mandates that the values being compared against the bottom/top should originate from the same comparator. This does not allow use cases such as cross comparator value comparisons i.e. if a user wanted to compute the "global" minimum across multiple comparators.
FieldComparators expose an API to get the feature value corresponding to a docID. We should let LeafFieldComparators do the same. A new comparison method is not required since the parent FieldComparator's compare method can be used once the values are retrieved.
Legacy Jira details
LUCENE-8949 by Atri Sharma (@atris) on Aug 12 2019, updated Sep 26 2019
We allow LeafFieldComparators to only accept a docID, get the equivalent feature value(s) and compare against the bottom/top of the values set for the comparator. This mandates that the values being compared against the bottom/top should originate from the same comparator. This does not allow use cases such as cross comparator value comparisons i.e. if a user wanted to compute the "global" minimum across multiple comparators.
FieldComparators expose an API to get the feature value corresponding to a docID. We should let LeafFieldComparators do the same. A new comparison method is not required since the parent FieldComparator's compare method can be used once the values are retrieved.
Legacy Jira details
LUCENE-8949 by Atri Sharma (@atris) on Aug 12 2019, updated Sep 26 2019