[
https://issues.apache.org/jira/browse/SOLR-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774221#comment-16774221
]
Avinash edited comment on SOLR-13261 at 2/21/19 4:25 PM:
-
Thanks for the patch Erick . The patch helps a great deal for our use case
especially since we have more than 300 fields defined in the schema .
Introduction of Sortable Text Field was great for us since it avoid duplication
of fields ( one for doc values one for lowercase filter factory) . Since most
of our fields were Sortable Text , this issue was limiting us in evaluating
Streaming expressions.
was (Author: avipatil):
Thanks for the patch Erick . The patch is helps a great deal for our use case
especially since we have more than 300 fields defined in the schema .
Introduction of Sortable Text Field was great for us since it avoid duplication
of fields ( one for doc values one for lowercase filter factory) . This was
also limiting us in evaluating streaming features of Solr.
> Should SortableTextField be allowed in export?
> --
>
> 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
> Attachments: 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
