[
https://issues.apache.org/jira/browse/SOLR-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054320#comment-13054320
]
Shalin Shekhar Mangar commented on SOLR-2610:
---------------------------------------------
{quote}
I can think of a corollary core action I'd like to see – the ability on a core
RELOAD to entirely delete the index from a core and replace it with a fresh
empty index that will start building at segment _0. I would do this to my
"build" core before using it, and later after swapping it with the "live" core
and ensuring it's good, to free up disk space.
{quote}
Shawn, that is not a use-case for RELOAD. The idea behind it is to reload an
existing core's index with updated configuration changes and swap it with the
existing core without causing downtime. It seems like your use-case is handled
well with the stock CREATE, SWAP and UNLOAD+deleteIndex?
> 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
