[
https://issues.apache.org/jira/browse/SOLR-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Stults updated SOLR-4647:
---
Attachment: SOLR-4647.patch
FieldType can interpret BytesRef correctly if you pass it SchemaField in the
toObject call. Subclasses override that like in StrField, where toObject
returns term.utf8ToString.
The attached patch takes that approach. There's also a unit test on string
fields that aren't stored or indexed, but have docValues. The test groups and
sorts by that docValues-only field.
> Grouping is broken on docvalues-only fields
> ---
>
> Key: SOLR-4647
> URL: https://issues.apache.org/jira/browse/SOLR-4647
> Project: Solr
> Issue Type: Bug
>Affects Versions: 4.2
>Reporter: Adrien Grand
> Labels: newdev
> Attachments: SOLR-4647.patch
>
>
> There are a few places where grouping uses
> FieldType.toObject(SchemaField.createField(String, float)) to translate a
> String field value to an Object. The problem is that createField returns null
> when the field is neither stored nor indexed, even if it has doc values.
> An option to fix it could be to use the ValueSource instead to resolve the
> Object value (similarily to NumericFacets).
--
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
