You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Eric Pugh (JIRA)" <ji...@apache.org> on 2018/10/25 14:56:00 UTC
[jira] [Commented] (SOLR-12925) Configsets API should allow update
of existing configset
[ https://issues.apache.org/jira/browse/SOLR-12925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663845#comment-16663845 ]
Eric Pugh commented on SOLR-12925:
----------------------------------
I have run into the same awkwardness... I have a script that uploads my security.json, and then packages up the configset and uploads it to Solr.
However, if I make changes to the schema through the Admin app, how do I preserve those locally? It's awkward to download the managed-schema.xml....
I've been experiementing with having "migrations" (inspired by Rails ActiveRecord) in my /configsets/my_config/migrations directory. It's a series of shell scripts in a numbered order, and I run them after uploading the configset to change things through the Schema API. At this point, I'm not sure if it helps or not!
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org