I was in the same situation recently. I think it would be nice to have the configset UPLOAD command be able to override the existing configset instead of just fail (with a parameter such as override=true or something). We need to be careful with the trusted/unstrusted flag there, but that should be possible.
> If we can’t modify the configset wholesale this way, is it possible to create a new configset and swap the old collection to it? You can create a new one and then call MODIFYCOLLECTION on the collection that uses it: https://lucene.apache.org/solr/guide/8_6/collection-management.html#modifycollection-parameters. I've never used that though. On Fri, Sep 11, 2020 at 7:26 AM Carroll, Michael (ELS-PHI) < m.carr...@elsevier.com> wrote: > Hello, > > I am running SolrCloud in Kubernetes with Solr version 8.5.2. > > Is it possible to update a configset being used by a collection using a > SolrCloud API directly? I know that this is possible using the zkcli and a > collection RELOAD. We essentially want to be able to checkout our configset > from source control, and then replace everything in the active configset in > SolrCloud (other than the schema.xml). > > We have a couple of custom plugins that use config files that reside in > the configset, and we don’t want to have to rebuild the collection or > access zookeeper directly if we don’t have to. If we can’t modify the > configset wholesale this way, is it possible to create a new configset and > swap the old collection to it? > > Best, > Michael Carroll >
