Thinking a little longer, and remembering the code a little more, I
suspect removing middle collections probably won't actually error (assuming
you actually wanted gaps in your time series and that you don't consider
that an error), but any new data that would have hit the removed collection
it would then be added to the next oldest one which will create a funny
double-wide "time slice". The other thing I should have mentioned is be
careful not to change the order of the collections. That will cause
problems because the search for the destination collection iterates the
collection list until it finds a collection with a start time (name) older
than the document. If you moved the first one it might try to re-create it
with the same name and start failing very noisily for every update...

On Mon, Apr 26, 2021 at 11:35 AM Gus Heck <gus.h...@gmail.com> wrote:

> If I understand your question correctly you have
>
>  1. A Time Routed Alias (TRA) already created
>  2. Data already indexed into the TRA .
>
> You now want to delete (presumably) the oldest collection referenced by
> this alias?
>
> There are two options here.
>
>  1. If you will always want to delete collections older than X one is to
> set the router.autoDeleteAge parameter for your TRA (see
> https://solr.apache.org/guide/8_8/collection-aliasing.html#time-routed-alias-parameters
> ), just re-send the original create command with the added parameter
>  2. If this is a one time thing (i.e. a mistake or something that requires
> human approval for business reasons) you can issue CREATEALIAS with a
> collections list omitting the oldest collections to remove them from the
> alias.
>
> WARNING: You MUST NOT remove middle or newest collections, since new data
> will recreate the newer ones (or fail if maxFutureMS is too small for it)
> and everything breaks down (documents going to wrong collections or errors)
> if there is a gap in the middle of a TRA. Once the tail collections are
> removed it is safe to delete them as with any normal collection.
>
>
>
> On Mon, Apr 26, 2021 at 10:01 AM Polzer, Christian <
> christian.pol...@atos.net> wrote:
>
>> Hello,
>>
>>
>>
>> We plan to use Solr8.8 and the Collection Aliasing for Time series data.
>> Unfortunately, I have nothing found to remove a collection from a
>> Collection Aliasing that it can be removed/deleted afterwards.
>>
>>
>>
>> My question: how can I remove a collection from a Collection Aliasing or
>> what is the best way to delete the referenced collection?
>>
>>
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> Christian Polzer
>>
>>
>>
>>
>> * Christian Polzer*
>> SW Engineer - Senior
>> Atos IT Solutions and Services GmbH
>> M. +43 664 88552369
>> christian.pol...@atos.net
>> Autokaderstr. 29
>>
>> 1210 Vienna, Austria
>>
>> atos.net <https://atos.net/en>
>>
>> [image: Atos]
>>
>> [image: linkedin][image: twitter] 
>> <https://twitter.com/atos_at?lang=de>[image:
>> xing][image: instagram] <https://www.instagram.com/atosglobal/?hl=de>
>>
>> Company Name: Atos Convergence Creators GmbH; Legal Form: Limited
>> Company; Company Seat: Vienna; Register Number: FN 386049w, Registered at:
>> Commercial Court Vienna; DVR-Number: 4009290
>>
>>
>>
>> This e-mail and the documents attached are confidential and intended
>> solely for the addressee; it may also be privileged. If you receive this
>> e-mail in error, please notify the sender immediately and destroy it. As
>> its integrity cannot be secured on the Internet, the Atos group liability
>> cannot be triggered for the message content. Although the sender endeavors
>> to maintain a computer virus-free network, the sender does not warrant that
>> this transmission is virus-free and will not be liable for any damages
>> resulting from any virus transmitted.
>>
>>
>>
>>
>>
>>
>> Company: Atos IT Solutions and Services GmbH
>> Legal form: Gesellschaft mit beschränkter Haftung
>> Company seat: Vienna
>> Commercial registry file nr.: FN 357865y
>> Commercial Court: Handelsgericht Wien
>> DVR: 4003754
>> ATU UID: 66190855
>> ARA Nr: 17961
>>
>> Important Note: This e-mail and the documents attached are confidential
>> and intended solely for the addressee; it may also be privileged. If you
>> receive this e-mail in error, please notify the sender immediately and
>> destroy it. As its integrity cannot be secured on the Internet, the Atos
>> group liability cannot be triggered for the message content. Although the
>> sender endeavors to maintain a computer virus-free network, the sender does
>> not warrant that this transmission is virus-free and will not be liable for
>> any damages resulting from any virus transmitted.
>>
>
>
> --
> http://www.needhamsoftware.com (work)
> http://www.the111shift.com (play)
>


-- 
http://www.needhamsoftware.com (work)
http://www.the111shift.com (play)

Reply via email to