[
https://issues.apache.org/jira/browse/SOLR-8387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048151#comment-15048151
]
Varun Thacker commented on SOLR-8387:
-------------------------------------
Thanks Erik for your feedback.
bq. Should this be applied to 5.x as well, since all the configs there
explicitly use ManagedSchemaFactory and the rename will happen after they have
started solr for the first time?
I think we should since {{example/files}} and {{data_driven}} configset do it
in 5.x too and if we don't do it, it will happen on startup anyways . So better
not to surprise the users.
> Solr example configs should ship with managed-schema instead of schema.xml
> --------------------------------------------------------------------------
>
> Key: SOLR-8387
> URL: https://issues.apache.org/jira/browse/SOLR-8387
> Project: Solr
> Issue Type: Improvement
> Affects Versions: Trunk
> Reporter: Varun Thacker
> Fix For: Trunk, 5.5
>
> Attachments: SOLR-8387.patch
>
>
> This is a followup of SOLR-8131 . In SOLR-8131 if a schema factory is not
> specified explicitly managed schema will be used.
> Now since managed schema factory is the default, when a user goes to start
> solr 6.0 their schema.xml file will get converted to managed-schema . This
> might seem trappy or confusing to a user. Hence why don't we directly ship
> with a a file called {{managed-schema}} instead of {{schema.xml}} . Just a
> rename of the files in all the example configs that we ship. The data_driven
> config does that already
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
