[
https://issues.apache.org/jira/browse/SOLR-11900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344455#comment-16344455
]
David Smiley commented on SOLR-11900:
-------------------------------------
I was chatting with [~gus_heck] and we figured the need for this isn't very
compelling (in either form above). Instead, if the user wants to delete old
collections explicitly, they could do these commands themselves (update the
alias, delete the collections). Collection deletion could even be enhanced to
detect its a part of an alias and auto-remove itself, which would make it
easier and would eliminate a race condition of the target collection list
getting updated at the same time more collections get added (however unlikely).
And after SOLR-11925, the user could also temporarily adjust whatever metadata
setting that establishes the automatic collection deletion time span, assuming
that new data is coming in to trigger the logic.
So I'll stop this now and re-use most of the code here in SOLR-11925 which
needs most of the same stuff.
> API command to delete oldest collections in a time routed alias
> ---------------------------------------------------------------
>
> Key: SOLR-11900
> URL: https://issues.apache.org/jira/browse/SOLR-11900
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Fix For: 7.3
>
> Attachments: SOLR-11900.patch
>
>
> For Time Routed Aliases, we'll need an API command to delete the oldest
> collection(s). Perhaps the command action name is
> DELETE_COLLECTION_OF_ROUTED_ALIAS (yes that's long). And input is of course
> the routed alias name, plus a mandatory "before" which is a standard time
> input that Solr accepts that will likely include date math. Thus if you used
> before="NOW/DAY-90DAYS" then your guaranteed to have the last 90 days worth
> of data. If a collection overlaps past what "before" is computed to be then
> it needs to stay. The pattern might match any number of collections, perhaps
> none. But in all cases, the most recent collection must be retained -- the
> time routed aliases must at all times refer to at least one collection.
> The underlying steps will be to first update the alias, and then delete the
> collection(s). It ought to return the collections that get deleted.
--
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
