[
https://issues.apache.org/jira/browse/SOLR-16194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536879#comment-17536879
]
Gus Heck commented on SOLR-16194:
---------------------------------
Fixing this will make it such that changing {{router.start}} won't clobber the
existing list (which should never happen when setting RA parameters). Although
it's not validated against, changing {{router.start}} will remain an expert
operation requiring manual creation of appropriate older collections and
updating the collection list in the alias manually. Tweaking start date without
these manual steps will potentially lead to a bloated initial collection.
Support for automating and bulletproofing changes to {{router.start}} type of
change would be beyond scope for this ticket. I'll check that we have good docs
on what's safe to tweak after the routed alias has data and what is not.
> Updating Time Routed Alias Parameters Loses Existing Collection List
> --------------------------------------------------------------------
>
> Key: SOLR-16194
> URL: https://issues.apache.org/jira/browse/SOLR-16194
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 8.11.1
> Reporter: Matt Kuiper
> Assignee: Gus Heck
> Priority: Major
>
> While updating a TRA with a new interval I noticed that the collection list
> stored in the alias.json is modified so that any previous created collections
> are dropped from the list and only the collection related to the TRA start
> date remains.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
