[
https://issues.apache.org/jira/browse/SOLR-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054415#comment-13054415
]
Mark Miller commented on SOLR-2610:
-----------------------------------
bq.I was approaching this particular issue more from the angle of making it
useful for SolrCloud.
where do you mention how this helps with SolrCloud?
bq. I can see how deleting configs can be useful to some people but is it worth
introducing such an inconsistency i.e. you can delete config but cannot add it
back? Anyways, it is best handled via a separate issue.
Why are you deleting cores only to add them back again with the same config? Do
you really think it's inconsistent to actually be able to delete something?
Does it really seem like a weird use case to say, I want to delete a SolrCore I
no longer have an interest in?
Looks like a few people have an interest in this issue, so I'm not sure why you
rammed it in so quickly.
> Add an option to delete index through CoreAdmin UNLOAD action
> -------------------------------------------------------------
>
> Key: SOLR-2610
> URL: https://issues.apache.org/jira/browse/SOLR-2610
> Project: Solr
> Issue Type: Improvement
> Components: multicore
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 3.3, 4.0
>
> Attachments: SOLR-2610-branch3x.patch, SOLR-2610.patch
>
>
> Right now, one can unload a Solr Core but the index files are left behind and
> consume disk space. We should have an option to delete the index when
> unloading a core.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
