2/27/2017 4:46 AM, Issei Nishigata wrote: > Thank you for your reply. If I was to say which one, I'd maybe be > talking about the concept for Solr. I understand we should use > "ClassicSchemaFactory" when we want to hand-edit, but why are there > two files, schema.xml and managed-schema, in spite that we can > hand-edit managed-schema? If we can modify the schema.xml through > Schema API, I think we won't need the managed-schema, but is there any > reason why that can't be done? Could you please let me know if there > is any information that can clear things up around those details?
The default filename with the Managed Schema factory is managed-schema -- no extension. I'm pretty sure that the reason the extension was removed was to discourage hand-editing. If you use both hand-editing and API modification, you can lose some (or maybe all) of your hand edits. The default filename for the schema with the classic factory is schema.xml. With this factory, API modification is not possible. If the managed factory is in use, and a schema.xml file is found during startup, the system will rename managed-schema (or whatever the config says to use) to something else, then rename schema.xml to managed-schema -- basically this is a startup-only way to support a legacy config. I personally don't ever plan to use the managed schema API, but I will leave the default factory in place, and hand-edit managed-schema, just like I did in previous versions with schema.xml. Thanks, Shawn
