[
https://issues.apache.org/jira/browse/SOLR-8387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker resolved SOLR-8387.
---------------------------------
Resolution: Fixed
Assignee: Varun Thacker
Next up SOLR-6019
> 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
> Assignee: Varun Thacker
> Fix For: Trunk, 5.5
>
> Attachments: SOLR-8387.patch, 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
