[
https://issues.apache.org/jira/browse/LUCENE-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647767#comment-15647767
]
Adrien Grand commented on LUCENE-7537:
--------------------------------------
bq. It defines 5 new sort types: sorted_string, sorted_long, sorted_double,
sorted_float, sorted_int and uses the Sorted{Set|Numeric}Selector for sorting.
The new types do not look useful to me? For instance,
{{DocValues.getSortedSet}} falls back to {{LeafReader.getSortedDocValues}} if
the reader does not have {{SORTED_SET}} doc values, so all the code that you
protected under eg. {{if (sortField.getType() ==
SortField.Type.SORTED_STRING)}} would also work with single-valued ({{SORTED}})
doc values (same for {{SORTED_NUMERIC}} and {{NUMERIC}} doc values).
> Add multi valued field support to index sorting
> -----------------------------------------------
>
> Key: LUCENE-7537
> URL: https://issues.apache.org/jira/browse/LUCENE-7537
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: Ferenczi Jim
> Attachments: LUCENE-7537.patch
>
>
> Today index sorting can be done on single valued field through the
> NumericDocValues (for numerics) and SortedDocValues (for strings).
> I'd like to add the ability to sort on multi valued fields. Since index
> sorting does not accept custom comparator we could just take the minimum
> value of each document for an ascending sort and the maximum value for a
> descending sort.
> This way we could handle all cases instead of throwing an exception during a
> merge when we encounter a multi valued DVs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
