[ 
https://issues.apache.org/jira/browse/SOLR-11033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436498#comment-16436498
 ] 

Varun Thacker commented on SOLR-11033:
--------------------------------------

How about this approach:
 * Remove the different languages them from the default configset
 * We don't add a kitchen_sink_configset 
 * When a user tries to create a collection using "./bin/solr create -c 
collection_name" provide a flag to "enable language support".  We'll use the 
SolrJ Schema API and add the necessary fieldtypes and dynamic fields 
It could even be more granular like "add all languages" or "add Japanese" if we 
want it to

> 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

Reply via email to