Apache
/
lucene
mirror of https://github.com/apache/lucene.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SOLR-8131: example/files config doesn't explicitly mention a schema factory + imporove upgrading instructions 

git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1718768 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Varun Thacker 2015-12-09 07:21:09 +00:00
parent d6b3312d82
commit a1605404b8
2 changed files with 5 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
solr/CHANGES.txt
View File

@ -69,8 +69,11 @@ Upgrading from Solr 5.x
See SOLR-8261 + SOLR-8329 for more details.
* If your solrconfig.xml file doesn't explicitly mention the schemaFactory to use then Solr will choose
the ManagedIndexSchemaFactory by default. This means that the Schema APIs ( /<collection>/schema )
are enabled by default and the schema is mutable. The schema file will be called managed-schema.
the ManagedIndexSchemaFactory by default. Previously it would have chosen ClassicIndexSchemaFactory.
This means that the Schema APIs ( /<collection>/schema ) are enabled and the schema is mutable.
When Solr starts your schema.xml file will be renamed to managed-schema. If you want to retain the old behaviour
then please ensure that the solrconfig.xml explicitly uses the ClassicIndexSchemaFactory :
<schemaFactory class="ClassicIndexSchemaFactory"/> or your luceneMatchVersion in the solrconfig.xml is less than 6.0
Detailed Change List
----------------------

22
solr/example/files/conf/solrconfig.xml
View File

@ -131,28 +131,6 @@
-->
<codecFactory class="solr.SchemaCodecFactory"/>
<!-- To disable dynamic schema REST APIs, use the following for <schemaFactory>:
<schemaFactory class="ClassicIndexSchemaFactory"/>
When ManagedIndexSchemaFactory is specified instead, Solr will load the schema from
the resource named in 'managedSchemaResourceName', rather than from schema.xml.
Note that the managed schema resource CANNOT be named schema.xml. If the managed
schema does not exist, Solr will create it after reading schema.xml, then rename
'schema.xml' to 'schema.xml.bak'.
Do NOT hand edit the managed schema - external modifications will be ignored and
overwritten as a result of schema modification REST API calls.
When ManagedIndexSchemaFactory is specified with mutable = true, schema
modification REST API calls will be allowed; otherwise, error responses will be
sent back for these requests.
-->
<schemaFactory class="ManagedIndexSchemaFactory">
<bool name="mutable">true</bool>
<str name="managedSchemaResourceName">managed-schema</str>
</schemaFactory>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Index Config - These settings control low-level behavior of indexing
Most example settings here show the default value, but are commented