I'm not sure changing something from mutable -> unmutable means it suddenly becomes hand-editable.
I don't know the details here, but I can imagine a case that unmutable implies some level of consistency, where the file is hashed, and later might be confirmed to still be the same 'unmutable' state. Hand editing would violate that contract. One might also imagine a future where 'managed-schema' isn't a config file, and is just an API you use to configure a Solr. In this case 'mutable' doesn't imply anything about files, just the state of the Solr config. -Doug On Sat, Jun 16, 2018 at 12:24 AM S G <sg.online.em...@gmail.com> wrote: > Hi, > > As per > > https://lucene.apache.org/solr/guide/7_2/schema-factory-definition-in-solrconfig.html#SchemaFactoryDefinitioninSolrConfig-Classicschema.xml > , > the only difference between schema.xml and managed-schema is that one > accepts schema-changes through an API while the other one does not. > > However, there is a flag "mutable" which can be used with managed-schema > too to turn dynamic-changes ON or OFF > > If that is true, then it means schema.xml does not offer anything which > managed-schema does not. > > Is that a valid statement to make? > > Infact, I see that schema.xml is not shipped anymore with Solr ? > > Thanks > SG > -- CTO, OpenSource Connections Author, Relevant Search http://o19s.com/doug
