[
https://issues.apache.org/jira/browse/SOLR-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050013#comment-15050013
]
Erick Erickson commented on SOLR-6980:
--------------------------------------
I think these two are a bit related at least.
I'm not sure I agree with this totally, I think there are two cases:
1> we upload a configset as part of collection creation, but creation fails.
Then it seems like we should surely remove the configset.
2> we just delete a collection and no other collection references it. In this
case I think it would be bad to delete the configset, even if it's not
associated with any other collection. Think of a user who deletes a collection
as part of their experimentation. Or to delete all the docs and start over. Or
is just testing the collection create/delete commands.
So barring a collection creation error, I think it's an invalid assumption that
just because a collection is deleted and no other collection references it,
it's not wanted.
> 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
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
