Hi, SOLR-7742 <https://issues.apache.org/jira/browse/SOLR-7742> introduced support for "immutable" config-sets in SOLR. This allows system administrators to define config-set templates a-priori (e.g. based on managed schema vs schemaless etc.) and then users can use configset APIs to define new configurations for the collections they want to create.
https://cwiki.apache.org/confluence/display/solr/ConfigSets+API One problem I notice here (based on Solr 6.3) is that when a user creates a new config-set by referring to an existing "immutable" config-set, the new config-set is also defined as "immutable" unless user explicitly specify immutable=false as part of the create operation. This is a bit problematic since Solr does not allow deleting an immutable config-set via an API. https://github.com/apache/lucene-solr/blob/0b817e6e495c40496b7cedc6f06060e43e5e2afc/solr/core/src/java/org/apache/solr/cloud/OverseerConfigSetMessageHandler.java#L369-L371 I think we should change this behavior so that when a user creates a new config set using an API, it is always mutable (i.e. immutable=false). This will enable users to delete the config sets they created using the API. What do you think? I can file a jira if this make sense. Thanks Hrishikesh
