lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7673) Add MultiValued[Int/Long/Float/Double]FieldSource for SortedNumericDocValues
Date Mon, 06 Feb 2017 18:21:41 GMT


David Smiley commented on LUCENE-7673:

Again; it can wait for another issue of course.  Your proposed name {{DoubleValuesSource.fromMultiValuedDoubleField(...)}}
seems plausible... or perhaps simply overload {{fromDoubleField(...)}} to have one that takes
the selector for how to treat a multi-valued field.

> Add MultiValued[Int/Long/Float/Double]FieldSource for SortedNumericDocValues
> ----------------------------------------------------------------------------
>                 Key: LUCENE-7673
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message