So, I am looking at the Solr 5.5 examples with their all-in by-default managed schemas. And I am scratching my head on the workflow users are expected to follow.
One example is straight from documentation: "With the above configuration, you can use the Schema API to modify the schema as much as you want, and then later change the value of mutable to false if you wish to "lock" the schema in place and prevent future changes." Which sounds great, except right above the definition in the solrconfig.xml, it says: "Do NOT hand edit the managed schema - external modifications will be ignored and overwritten as a result of schema modification REST API calls." And the Config API does not seem to provide any API to switch that property (schemaFactory.mutable is not an editable property). So, how is one supposed to lock the schema after modifying it? In the default, non-cloud, example! So far, the nearest I get is to unload the core (losing core.properties), manually modify solrconfig.xml in violation of instructions and add the core back. What am I missing? Regards, Alex. ---- Newsletter and resources for Solr beginners and intermediates: http://www.solr-start.com/
