You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alex Halovanic (JIRA)" <ji...@apache.org> on 2018/10/25 13:51:00 UTC

[jira] [Created] (SOLR-12925) Configsets API should allow update of existing configset

Alex Halovanic created SOLR-12925:
-------------------------------------

             Summary: Configsets API should allow update of existing configset
                 Key: SOLR-12925
                 URL: https://issues.apache.org/jira/browse/SOLR-12925
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
          Components: configset-api
    Affects Versions: 6.6.5, master (8.0)
            Reporter: Alex Halovanic


With the Configsets API it is not possible to update a configset once it has been created: the UPLOAD action will throw an exception "The configuration X already exists in zookeeper".  This is different behavior than the [other mechanisms|https://lucene.apache.org/solr/guide/using-zookeeper-to-manage-configuration-files.html] that allow uploading either a new or updated configuration to Zookeeper.

For someone trying to update a configuration, the only path given through the APIs is to delete the associated collection and configuration and start over from scratch. That, or a one-off invocation of the zk local scripts when these APIs are far superior for remote management (y).

 

Thanks,
 Alex



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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