[
https://issues.apache.org/jira/browse/SOLR-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591840#comment-16591840
]
Erick Erickson edited comment on SOLR-8008 at 8/24/18 3:52 PM:
---------------------------------------------------------------
I ran across this looking for something else. I propose we just close it as
"won't fix". We have the configsets api and bin/solr is another way to approach
it so I think we have enough tools to deal with this issue.
I'll close it over the weekend unless there are objections.
was (Author: erickerickson):
I ran across this looking for something else. I propose we just close it as
"won't fix". We have the configsets api and bin/solr is another way to approach
it so I think we have enough tools to deal with this issue.
> bin/solr should delete configset if collection creation fails and no other
> collection references it
> ---------------------------------------------------------------------------------------------------
>
> Key: SOLR-8008
> URL: https://issues.apache.org/jira/browse/SOLR-8008
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Major
>
> A user's list question prompted this, and at least two other devs hit it so
> I'm not imagining things.
> The bin/solr script (and SolrCLI) for create_collection uploads the config
> set automatically if (and only if) it's not in ZK already. But...
> Let's say I have a problem with my config files (syntax error, deprecated
> options, whatever) that prevents the collection from being created. It gets
> pretty confusing to correct the configs and try to create your collection
> again and have it fail for the same reason because the configs weren't
> re-uploaded to ZK.
> I can think of at least three+ options:
> 1> delete the configsets from ZK in collection failure case if (and only if)
> it isn't referenced by another collection. I like this one as, from a user's
> perspective, it's least confusing. I see my collection creation failed
> because of a problem in my configs. I correct the configs and do the exact
> same operation again and it succeeds.
> 1a> provide a "force configset update" option for create_collection. This
> one's easiest I think.
> 2> Provide an upload_configset option that overwrites an existing configset.
> Perhaps with a -force flag to insure it's done intentionally.
> 3> make the delete collection option remove a configset named identically to
> the collection even if the collection doesn't exist.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
