[
https://issues.apache.org/jira/browse/SOLR-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661380#comment-14661380
]
Shawn Heisey commented on SOLR-7895:
------------------------------------
bq. Once a commit happens, Lucene notices that there are no segments left, and
you are left with an entirely empty index.
Do you happen to know when this optimization was added? Last time I explicitly
checked (which I admit was quite a while ago), deleting all the docs in the
index didn't clear up disk space. When my build program starts a full rebuild
(with DIH), I have it do the following sequence on each build core: delete all
docs, commit, optimize, and then reload the core. That takes care of the disk
space... but if I had the option, I'd delete the data directory and reload.
The build program runs on another host and only connects with SolrJ, there is
no filesystem access.
> Administrative UI Lacks Obvious "Delete Core Contents" Button
> -------------------------------------------------------------
>
> Key: SOLR-7895
> URL: https://issues.apache.org/jira/browse/SOLR-7895
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 5.2.1
> Reporter: Aaron Greenspan
>
> When Solr screws up, which is practically on a daily basis, I often want to
> delete the contents of a core without deleting its structure. Instead of
> clicking on a button and perhaps an "Are you sure?" prompt, I have to
> remember this incredibly unwieldy and dangerous-to-bookmark URL:
> http://[server]:8983/solr/[core
> name]/update?stream.body=%3Cdelete%3E%3Cquery%3Eid:*%3C/query%3E%3C/delete%3E&commit=true
> To say that this is not user-friendly is a gross understatement. If there is
> a better way or an obvious easy way, I have not found it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
