[
https://issues.apache.org/jira/browse/SOLR-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784757#comment-16784757
]
Erick Erickson commented on SOLR-13261:
---------------------------------------
"except in this case we didn't tell you about, HA HA!!!""
Wouldn't be the first time ;)
OK, seriously. The solution here, then, is to refuse to export the field unless
useDocValuesAsStored=true, right? And throw an error out if someone attempts
to. And write a test proving it.
I can do that if you agree that's the correct solution.
And thanks for pointing this out....
> Make SortableTextField work with export/streaming
> -------------------------------------------------
>
> Key: SOLR-13261
> URL: https://issues.apache.org/jira/browse/SOLR-13261
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.7, 8.0, master (9.0)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Major
> Fix For: master (9.0), 8.1
>
> Attachments: SOLR-13261.patch, SOLR-13261.patch
>
>
> ExportWriter (and perhaps other places) explicitly tests for certain field
> types and error out with "Export fields must either be one of the following
> types: int,float,long,double,string,date,boolean"
> It seems perfectly legal to export SortableTextField as well as it's a DV
> field. How desirable that would be is an open question.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
