[
https://issues.apache.org/jira/browse/SOLR-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729865#comment-16729865
]
Gus Heck commented on SOLR-6399:
--------------------------------
This also seems like it would be useful for A/B testing schema configurations
on the same hardware if "unloaded" truly meant no resources were consumed.
Imagine one tries a change and it's worse not better. It would be nice to be
able to delete the experiment and simply reload the old collection. If the
change is good delete (or back up and archive) the old one... saves standing up
extra hardware, or re-indexing or backup/restore of the old collection when the
experiment fails. The bigger the cluster and the bigger the data set the more
useful this is.
> Implement unloadCollection in the Collections API
> -------------------------------------------------
>
> Key: SOLR-6399
> URL: https://issues.apache.org/jira/browse/SOLR-6399
> Project: Solr
> Issue Type: New Feature
> Reporter: dfdeshom
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Fix For: 6.0
>
>
> There is currently no way to unload a collection without deleting its
> contents. There should be a way in the collections API to unload a collection
> and reload it later, as needed.
> A use case for this is the following: you store logs by day, with each day
> having its own collection. You are required to store up to 2 years of data,
> which adds up to 730 collections. Most of the time, you'll want to have 3
> days of data loaded for search. Having just 3 collections loaded into memory,
> instead of 730 will make managing Solr easier.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
