You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Abhishek Kumar Singh (JIRA)" <ji...@apache.org> on 2017/12/30 14:40:00 UTC
[jira] [Comment Edited] (SOLR-11624) collection creation should not
also overwrite/delete any configset but it can!
[ https://issues.apache.org/jira/browse/SOLR-11624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306797#comment-16306797 ]
Abhishek Kumar Singh edited comment on SOLR-11624 at 12/30/17 2:39 PM:
-----------------------------------------------------------------------
Also, Thanks for pointing this consistency out.
bq. so if we have one configSet in ZooKeeper named "myconfig" and the user creates a collection "mycoll" (without specifying which config), then presumably we'll have two configSets: "myconfig" and "mycoll.AUTOCREATED_CONFIGSET". And this point there is no longer one configSet in ZooKeeper, nor is there "_default" for that matter. Does this mean if the user goes to create another collection similarly that it will fail?
I think yes, it will fail.
Looks like with the new ConfigName being added, this feature in particular will break.
We can get rid of this proble by
* Either depricating this feature of [using the only configset present|https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/cloud/CreateCollectionCmd.java#L362],
* Or making a new configSet named {{_default}} , whenever such a case arises.
[~dsmiley] [~ichattopadhyaya]
was (Author: abhidemon):
Also, Thanks for pointing this consistency out.
bq. so if we have one configSet in ZooKeeper named "myconfig" and the user creates a collection "mycoll" (without specifying which config), then presumably we'll have two configSets: "myconfig" and "mycoll.AUTOCREATED_CONFIGSET". And this point there is no longer one configSet in ZooKeeper, nor is there "_default" for that matter. Does this mean if the user goes to create another collection similarly that it will fail?
I think yes, it will fail.
Looks like with the new ConfigName being added, this feature in particular will break.
We can get rid of this proble by
* Either depricating this feature of [using the only configset present|https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/cloud/CreateCollectionCmd.java#L362],
* Or making a new configSet named {{_default}} , whenever such a case arises.
> collection creation should not also overwrite/delete any configset but it can!
> ------------------------------------------------------------------------------
>
> Key: SOLR-11624
> URL: https://issues.apache.org/jira/browse/SOLR-11624
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.2
> Reporter: Erick Erickson
> Assignee: Ishan Chattopadhyaya
> Attachments: SOLR-11624-2.patch, SOLR-11624.3.patch, SOLR-11624.4.patch, SOLR-11624.patch, SOLR-11624.patch
>
>
> Looks like a problem that crept in when we changed the _default configset stuff.
> setup:
> upload a configset named "wiki"
> collections?action=CREATE&name=wiki&.....
> My custom configset "wiki" gets overwritten by _default and then used by the "wiki" collection.
> Assigning to myself only because it really needs to be fixed IMO and I don't want to lose track of it. Anyone else please feel free to take it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org