anchor.diff:    added at the front of the TRA.
     TRUP will create this collection, add it to the alias and then forward the document to the collection it just created.
     This can happen recursively if more than one collection needs to be created.
  -  Each time a new collection is added, the oldest collections in the TRA are examined for possible deletion, if that has
  ++
  +Each time a new collection is added, the oldest collections in the TRA are examined for possible deletion, if that has
       been configured.
  -  All this happens synchronously, potentially adding seconds to the update request and indexing latency.
  +All this happens synchronously, potentially adding seconds to the update request and indexing latency.
   
   Any other type of update like a commit or delete is routed by TRUP to all collections.
   Generally speaking, this is not a performance concern. When Solr receives a delete or commit wherein nothing is deleted
  
positive.code: 
  * Only *time* routed aliases are supported.  If you instead have some other sequential number, you could fake it
    as a time (e.g., convert to a timestamp assuming some epoch and increment).
    The smallest possible interval is one second.
    No other routing scheme is supported, although this feature was developed with considerations that it could be
    extended/improved to other schemes.
  
  * The underlying collections form a contiguous sequence without gaps.  This will not be suitable when there are
  
negative.code: = Time Routed Aliases
  
  Time Routed Aliases (TRAs) is a SolrCloud feature that manages an alias and a time sequential series of collections.
  
  It automatically creates new collections and (optionally) deletes old ones as it routes documents to the correct
    collection based on its timestamp.
  This approach allows for indefinite indexing of data without degradation of performance otherwise experienced due to the
    continuous growth of a single index.
  
  If you need to store a lot of timestamped data in Solr, such as logs or IoT sensor data, then this feature probably
    makes more sense than creating one sharded hash-routed collection.
  
  == How It Works
  
  First you create a time routed aliases using the <<collections-api.adoc#createalias,CREATEALIAS>> command with some
    router settings.
  Most of the settings are editable at a later time using the <<collections-api.adoc#aliasprop,ALIASPROP>> command.
  
  The first collection will be created automatically, along with an alias pointing to it.
  Each underlying Solr "core" in a collection that is a member of a TRA has a special core property referencing the alias.
  The name of each collection is comprised of the TRA name and the start timestamp (UTC), with trailing zeros and symbols
  