Hi, We're transitioning from Solr 4.10 to 7.x and working through our options around managing our schemas. Currently we manage our schema files in a git repository, make changes to the xml files, and then push them out to our zookeeper cluster via the zkcli and the upconfig command like:
/apps/solr/bin/zkcli.sh -cmd upconfig -zkhost host.com:9580 -collection core -confname core -confdir /apps/solr/cores/core/conf/ -solrhome /apps/solr/ This allows us to deploy schema changes without restarting the cluster, while maintaining version control. It looks like we could do the exact same process using Solr 7 and the solr control script like bin/solr zk upconfig -z 111.222.333.444:2181 -n mynewconfig -d /path/to/configset Now of course we'd like to improve this process if possible, since manually pushing schema files to the ZK server and reloading the cores is a bit command line intensive. Does anyone has any guidance or experience here leveraging the managed schema api to make updates to a schema in production while maintaining a version controlled copy of the schema. I'd considered using the api to make changes to our schemas, and then saving off the generated schema api to git, or saving off a script that creates the schema file using the managed api to git, but I'm not sure if that is any easier or just adds complexity. Any thoughts or experience appreciated. Thanks, TZ
