Varun Thacker commented on SOLR-12006:

This should be fine from a back-compat point of view as well since people using 
"_txt" fields will still use it as multi-valued.

> Add back '*_t' dynamic field for single valued text fields
> ----------------------------------------------------------
>                 Key: SOLR-12006
>                 URL: https://issues.apache.org/jira/browse/SOLR-12006
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Varun Thacker
>            Assignee: Varun Thacker
>            Priority: Major
>         Attachments: SOLR-12006.patch
> Solr used to have a '_t' dynamic field which was single valued and a "_txt" 
> field for multi-valued text 
> Solr 4.x : 
> [https://github.com/apache/lucene-solr/blob/branch_4x/solr/example/example-schemaless/solr/collection1/conf/schema.xml#L129]
> Somewhere in Solr 5.x both became the same definition . 
> [https://github.com/apache/lucene-solr/blob/branch_5_4/solr/server/solr/configsets/data_driven_schema_configs/conf/managed-schema#L138]
> In master now there is no "_t" dynamic field anymore. 
> We have a single-valued dynamic field and multi-valued dynamic field for 
> ints, longs, boolean, float, date , string . We should provide the same 
> option for a text field

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to