[
https://issues.apache.org/jira/browse/SOLR-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285680#comment-14285680
]
Erik Hatcher commented on SOLR-6966:
------------------------------------
bq. ...identify text as string, and create a copyField src="*" dst="_all" which
is of type text, and use this as df by default.
You mean like the 5x data_driven_schema managed schema out of the box
configuration?
{code}
<field name="_text" type="text_general" indexed="true" stored="false"
multiValued="true"/>
<copyField source="*" dest="_text"/>
{code}
What is d_d_s lacking?
> For Data Driven Schema, consider multi-word text fields to be text, not
> string field types
> ------------------------------------------------------------------------------------------
>
> Key: SOLR-6966
> URL: https://issues.apache.org/jira/browse/SOLR-6966
> Project: Solr
> Issue Type: Improvement
> Reporter: Grant Ingersoll
>
> A tricky situation, for sure, but I suspect in data-driven mode, when field
> guessing, we should treat multi-word strings as text by default, not String,
> so that the user's first experience is they can search against that field.
> Alternatively, create a second field that is either the String version or the
> Text version.
> Even more advanced option: use pseudo-fields (like what we do for some
> spatial) and intelligently use one or the other depending on the context:
> e.g. faceting uses the one form, search uses the other.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
