[
https://issues.apache.org/jira/browse/SOLR-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-10835:
----------------------------
Priority: Blocker (was: Major)
setting as blocker since the test failures now leave this "fix" in an amorphous
state for the purposes of tracking against 7.0
[~tomasflobbe]: can you please dig in and figure out if these test failures
represent a failure in the code added as part of this issue that should also be
resolved as part of this issue, or a test bug introduced by this issue that can
be fixedup easily, or a distinct previously unknown bug that was surfaced by
your increased test coverage that should be tracked/prioritized in it's own new
jira?
> 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
> Priority: Blocker
> Fix For: 7.0, 6.7
>
> 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]
