[
https://issues.apache.org/jira/browse/SOLR-11033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423244#comment-16423244
]
Varun Thacker commented on SOLR-11033:
--------------------------------------
I'm not sure I'm sold on implict field types . How would one configure the
synonyms / stopwords files for the implicit field_types ? It just makes things
less transparent from what I am thinking right now
The other idea could we we remove all the language specific field_types and
dynamic fields from the default schema. Then create a page under
[http://lucene.apache.org/solr/guide/7_2/documents-fields-and-schema-design.html]
called "Language FieldTypes" where we add curl commands to each of the current
field-types that are out there in the default schema. And in the managed-schema
just leave a comment to the ref-guide page
> Move out multi language field and fieldType to a separate example
> ------------------------------------------------------------------
>
> Key: SOLR-11033
> URL: https://issues.apache.org/jira/browse/SOLR-11033
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: examples
> Reporter: Varun Thacker
> Priority: Major
>
> The bulk of the schema file in the default configset has fieldType and
> dynamic field definition for different languages. Based on the discussion
> on SOLR-10967 if we move it to a separate config set and keep the default
> configset english only then the size will be dramatically reduced and make
> the schema file much more readable.
--
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
