[
https://issues.apache.org/jira/browse/SOLR-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785877#comment-16785877
]
Hoss Man commented on SOLR-13261:
---------------------------------
{quote}I can do that if you agree that's the correct solution.
{quote}
That's my suggestion, yes – i think there is an argument to be made that
/export should do that for *all* fields, but obviously that might be
problematic from a back compat standpoint.
If people disagree and think that /export should _never_ care about
useDocValuesAsStored then at a minimum the docs (of both /export and
SortableTextField) need to be updated to be very clear about the fact that
/exported values are not garunteed to be "complete" – and in the
SortableTextField case will be truncated.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
