[jira] [Created] (SOLR-8863) zkcli: provide more granularity in config manipulation

["Shawn Heisey (JIRA)" <ji...@apache.org>]

Shawn Heisey created SOLR-8863:
----------------------------------

             Summary: zkcli: provide more granularity in config manipulation
                 Key: SOLR-8863
                 URL: https://issues.apache.org/jira/browse/SOLR-8863
             Project: Solr
          Issue Type: Improvement
          Components: scripts and tools, SolrCloud
    Affects Versions: 5.5
            Reporter: Shawn Heisey
            Priority: Minor


I was thinking about what somebody has to do if they want to replace a single file in a specific SolrCloud configuration.  This and other operations could be easier with some tweaks to the zkcli program.

I'd like to have some options to do things like the following, and other combinations not specifically stated here:

 * Upload the file named solrconfig.xml to the 'foo' config.
 * Upload the file named solrconfig.xml to the config used by the 'bar' collection.
 * Download the file named stopwords.txt from the config used by the 'bar' collection.
 * Rename schema.xml to managed-schema in the 'foo' config.
 * Delete archaic_stopwords.txt from the config used by the 'bar' collection.

When a config is changed, it would be a good idea for the program to print out a list of all collections affected by the change.  I can imagine a "-interactive" option that asks "are you sure" after printing the affected collection list, and a "-dry-run" option to print out that information without actually doing anything.  An alternative to the interactive option -- have the program prompt by default and implement a "-force" option to do it without prompting.

I wonder whether it would be a good idea to include an option to reload all affected collections after a change is made.  The script uses WEB-INF/lib on the classpath, so SolrJ should be available.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org