[
https://issues.apache.org/jira/browse/SOLR-11033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079721#comment-16079721
]
Jan Høydahl commented on SOLR-11033:
------------------------------------
Have you considered the possibility for "implicit" field types? Just as we have
implicit request handlers in solrconfig (e.g. /admin) one could argue that the
system could register some field types automatically and perhaps even lazily.
Such types could be defined in a separate {{system_field_types.json}} file on
schema-api format, resolved on class path, and if a user defines same type name
in his schema.xml then that could override the system default, which would give
perfect backward compat.
Such a implicit default would need to be handled with care wrt back-compat. We
could say that we add system_field_types_7_1.json instead of changing the 7_0
one, and use luceneMatchVersion to choose which one to load, not to break users
expectations. Benefit is that we could also factor out all the other fieldTypes
and the default schema becomes very slim...
> 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)
> Reporter: Varun Thacker
>
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
