[ https://issues.apache.org/jira/browse/SOLR-7570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563258#comment-14563258 ]
Noble Paul commented on SOLR-7570: ---------------------------------- * Do we have a plan on the backcompat ? What happens to the existing configoverlay.json etc ? * What happens if I really wish to store the config changes shared between collections. It is a common usecase > Config APIs should not modify the ConfigSet > ------------------------------------------- > > Key: SOLR-7570 > URL: https://issues.apache.org/jira/browse/SOLR-7570 > Project: Solr > Issue Type: Improvement > Reporter: Tomás Fernández Löbbe > Attachments: SOLR-7570.patch > > > Originally discussed here: > http://mail-archives.apache.org/mod_mbox/lucene-dev/201505.mbox/%3CCAMJgJxSXCHxDzJs5-C-pKFDEBQD6JbgxB=-xp7u143ekmgp...@mail.gmail.com%3E > The ConfigSet used to create a collection should be read-only. Changes made > via any of the Config APIs should only be applied to the collection where the > operation is done and no to other collections that may be using the same > ConfigSet. As discussed in the dev list: > When a collection is created we should have two things, an immutable part > (the ConfigSet) and a mutable part (configoverlay, generated schema, etc). > The ConfigSet will still be placed in ZooKeeper under "/configs" but the > mutable part should be placed under "/collections/$COLLECTION_NAME/…" > [~romseygeek] suggested: > {quote} > A nice way of doing it would be to make it part of the SolrResourceLoader > interface. The ZK resource loader could check in the collection-specific > zknode first, and then under configs/, and we could add a writeResource() > method that writes to the collection-specific node as well. Then all config > I/O goes via the resource loader, and we have a way of keeping certain parts > immutable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org