[
https://issues.apache.org/jira/browse/SOLR-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-6980.
----------------------------------
Resolution: Won't Fix
Thinking about this, I think it's a bad idea to remove configsets. We routinely
ask people to delete a collection and reindex, say to add docValues=true or
when upgrading a major version. One way people do this is to delete the
collection and start over. If we deleted the configset at that point they'd
lose their old schema.
The configsets api will allow these to be cleaned up without having to use
zkCli or the like so I think it's best to not do anything.
If anyone wants to pick this up, feel free to reopen.
> Collection deletion, creation and shared configsets
> ---------------------------------------------------
>
> Key: SOLR-6980
> URL: https://issues.apache.org/jira/browse/SOLR-6980
> Project: Solr
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Assignee: Erick Erickson
> Priority: Major
>
> If a configset is not being shared and a collection is deleted, I think we
> should also delete the configset, or at least the copy of it for that
> collection.
> You can see the ill effects of this by doing:
> # create a data-driven schema collection
> # index some content to it, thus materializing an actual schema
> # delete the collection
> # create a new collection w/ the same name
> # observe that the new collection has the old materialized schema
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
