On 6/18/2015 8:10 AM, Steven White wrote: > In 5.1.0 (and maybe prior ver.?) when I enable managed schema per the > above, the existing schema.xml file is left as-is, a copy of it is created > as schema.xml.bak and a new one is created based on the name I gave it > "my-schema.xml". > > With 5.2.1 schema.xml is renamed to schema.xml.bak and my-schema.xml is > created (e.g.: schema.xml is deleted). > > Is this an expected behavior or is this a bug? I see it as a bug because > if I revert the change I made in my solrconfig.xml back to (i.e.: not > managed schema any more): > > <schemaFactory class="ClassicIndexSchemaFactory"/> > > Solr will not restart because it cannot find schema.xml
As I understand it, the managed schema system will complain if it sees a file named schema.xml -- having both the managed schema file and schema.xml is confusing, so if the classic file exists, it's an error. Because of that, if you switch your config from managed to classic schema, you must also create the schema.xml file (or rename the managed version). Neither factory is aware of the other, so there's no automated way to handle that. Thanks, Shawn
