[ 
https://issues.apache.org/jira/browse/SOLR-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784637#comment-16784637
 ] 

Hoss Man commented on SOLR-13261:
---------------------------------

bq. Having the same limitation apply to DV seems consistent. Whether it's right 
or not is what we're debating I suppose.

well -- my point is that this debate already took place in SOLR-11916 when 
SortableTextField was added, and the concensus there was that it was dangerous 
to let users think they could get the original value back from the "doc value" 
when what they would actually get back is a truncated value.  which is why the 
field was updated to behave differently at index time if the user set 
useDocValuesAsStored="true" and maxCharsForDocValues was exceeded -- so there 
was never any "suprise" risk of returning truncated values at "query fl" time.

you've created the exact same situation at "export fl" time -- but if anything 
you've made the trap twice as bad because (as mentioned) the docs for this 
field type as written make a big deal out of how/why this field defaults to 
useDocValuesAsStored="false" to protect users from this trap, but in the export 
code path this isn't respected ... so the documentation now seems like a 
missleading bait and switch.  "We will protect you from getting truncated 
values ... except in this case we didn't tell you about, HA HA!!!"



> 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]

Reply via email to