[
https://issues.apache.org/jira/browse/SOLR-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047102#comment-16047102
]
ASF subversion and git services commented on SOLR-10835:
--------------------------------------------------------
Commit db91fb7927bd82b6507c9c2aeece633f05f65070 in lucene-solr's branch
refs/heads/branch_6x from [~tomasflobbe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=db91fb7 ]
SOLR-10835: Add support for point fields in Export Handler
> ExportWriter only works with TrieFooFields, not FooPointFields
> --------------------------------------------------------------
>
> Key: SOLR-10835
> URL: https://issues.apache.org/jira/browse/SOLR-10835
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Assignee: Tomás Fernández Löbbe
> Attachments: SOLR-10835.patch, SOLR-10835.patch, SOLR-10835.patch
>
>
> ExportWriter explicitly fails hard if you attempt to use it with any of the
> new Numeric Points based fields.
> The current failures come from explicit {{if (fieldType instanceof
> TrieFooField)}} checks in {{ExportWriter.getFieldWriters}} -- those could
> probably be replaced with {{instanceof FooValueFieldType}} (the numeric
> marker interfaces) or {{getNumericType()}} but i suspect in the multivalued
> case other problems will arise due to how ExportWriter dips into the guts of
> DocValues and assumes SortedSetDocValues
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
