lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (SOLR-11722) API to create a Time Routed Alias and first collection
Date Mon, 01 Jan 2018 16:54:00 GMT


David Smiley commented on SOLR-11722:

RE V2/V1, the "properties" mechanism looks promising.  I think it's totally fine to have _introspect
not expose the collection creation particulars of time routed alias. We can add docs to help
users knows some do's and don'ts.

Yeah naming stuff is hard.  I'm good with "collection-create"; it's not bad.

RE alias routing, I think it's a dead-end to try to invent names similar to "router" but not
use "router" simply because shards have a router using the name "router". This is the same
concept, but we are applying it to this new "routed alias" thing as opposed to shards.  And
we have a new type/name expressly for time routing.  If some new thing comes along in Solr
that might be routed (which I admit seems unlikely), it might then also try to avoid using
the "route" word... hence it feels wrong to try to have them use separate words.  It's the
same concept.  But since the location of use is different that gives context, I think it's
fine to use the same parameters as there isn't ambiguity.  Here we're adding alias metadata
parameters, and so it applies to the alias.  In collection creation, the router is name-spaced
in the context of _that_.  Hence I propose we use these metadata fields:,
router.field=myTimestampField, router.interval=+1DAY, and it's debatable if TZ is router.TZ
or just TZ.  "start" isn't metadata, it's a param of this command that isn't used after.

> API to create a Time Routed Alias and first collection
> ------------------------------------------------------
>                 Key: SOLR-11722
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: David Smiley
>         Attachments: SOLR-11722.patch
> This issue is about creating a single API command to create a "Time Routed Alias" along
with its first collection.  Need to decide what endpoint URL it is and parameters.
> Perhaps in v2 it'd be {{/api/collections?command=create-routed-alias}} or alternatively
piggy-back off of command=create-alias but we add more options, perhaps with a prefix like
> Inputs:
> * alias name
> * misc collection creation metadata (e.g. config, numShards, ...) perhaps in this context
with a prefix like "collection."
> * metadata for TimeRoutedAliasUpdateProcessor, currently: router.field
> * date specifier for first collection; can include "date math".
> We'll certainly add more options as future features unfold.
> I believe the collection needs to be created first (referring to the alias name via a
core property), and then the alias pointing to it which demands collections exist first. 
When figuring the collection name, you'll need to reference the format in TimeRoutedAliasUpdateProcessor.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message