[
https://issues.apache.org/jira/browse/LUCENE-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854587#comment-15854587
]
ASF subversion and git services commented on LUCENE-7673:
---------------------------------------------------------
Commit c9c3fb489c822e0f46927167b39911e9ec7ac52a in lucene-solr's branch
refs/heads/branch_6x from Tomas Fernandez Lobbe
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c9c3fb4 ]
LUCENE-7673: Add MultiValued[Int/Long/Float/Double]FieldSource for
SortedNumericDocValues
> Add MultiValued[Int/Long/Float/Double]FieldSource for SortedNumericDocValues
> ----------------------------------------------------------------------------
>
> Key: LUCENE-7673
> URL: https://issues.apache.org/jira/browse/LUCENE-7673
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Tomás Fernández Löbbe
> Assignee: Tomás Fernández Löbbe
> Attachments: LUCENE-7673.patch
>
>
> Right now \[Int/Long/Float/Double\]FieldSource can give a {{ValueSource}}
> view of a {{NumericDocValues}} field. This Jira is to add
> MultiValued\[Int/Long/Float/Double\]FieldSource that given a
> {{SortedNumericSelector.Type}} can give a {{ValueSource}} view of a
> {{SortedNumericDocValues}} field
> I considered instead of adding new classes an optional selector parameter to
> the existing \[Int/Long/Float/Double\]FieldSource, but I think adding
> different classes makes a cleaner API and it’s clear that for MultiValued*
> case, the selector is a mandatory parameter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
