where do you mention how this helps with SolrCloud?
I didn't and I'm sorry about that. I was just trying to tell you my perspective. These are small pieces that need to be fixed before tackling larger problems in SolrCloud and this one seemed generally useful and simple enough by itself that I opened the issue without giving the bigger picture. Some of the other pieces are captured in
Why are you deleting cores only to add them back again with the same config?
SOLR-2595 will give you a better idea of what I was thinking. The use-case is to split and migrate pieces of an index and this issue will help in deleting the leftover temporary cores.
Do you really think it's inconsistent to actually be able to delete something?
The inconsistency is to be able to delete a configuration file when there is no way to add it back but I'm not against the feature in general.
Does it really seem like a weird use case to say, I want to delete a SolrCore I no longer have an interest in?
Absolutely not. If you want that feature, that's fine. You don't need permissions to put up a patch and commit it
Looks like a few people have an interest in this issue, so I'm not sure why you rammed it in so quickly.
The issue clearly talks about deleting index on unload and that's what it does. And I got a +1 from you and Jason on the topic of the issue (or at least, that's what I assumed). I waited a day to commit - would you like me to wait longer for future issues or leave a comment to that effect? If the patch is not what you intended, go ahead and reopen/extend the scope of the issue or open another issue.