[
https://issues.apache.org/jira/browse/SOLR-12006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370812#comment-16370812
]
Varun Thacker commented on SOLR-12006:
--------------------------------------
The approach taken in this patch will break back-compat if a user was expecting
"text_general" to be multi-valued but now isn't.
It doesn't break if you were using dynamic fields but if you were defining a
new field and using fieldType=text_general ( like "add-schema-fields" does in
our solrconfig ) then that will break.
The approach we could take is explicitly making the dynamic field "_t"
multiValued=false
I'll post a patch soon with that approach
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
