[
https://issues.apache.org/jira/browse/SOLR-12925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675318#comment-16675318
]
Alex Halovanic commented on SOLR-12925:
---------------------------------------
Thank you for the suggestions: I have been version controlling my configsets
like this, but my big difficulty was that I was in a remote deployment
environment (Windows PowerShell) where forcing in Java and a significant
fraction of the Solr install/ZooKeeper configuration would have been very
awkward.
I have now found one REST-only approach to get around this limitation that
seems to be working for me:
# Use the CREATE action in the ConfigSets API to copy the existing configset
to a temporary name.
# Use the MODIFYCOLLECTION action in the Collections API to alter
collection.configName to this temporary name.
# Reload the collection.
# Delete the original (now unused) configset.
# Upload the updated configset under the original name.
# Modify the collection back to the original configset name.
# Reload the collection.
# Delete the temporary configset.
So this isn't entirely impossible, but it is still cumbersome with 4x as many
steps as the command line.
> 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
> Priority: Minor
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
