[
https://issues.apache.org/jira/browse/SOLR-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217655#comment-16217655
]
David Smiley commented on SOLR-11542:
-------------------------------------
*Proposed collection alias metadata:*
* The document field containing the timestamp to route on. What to call this?
I'm not sure. Perhaps it should contain "router.field" as a suffix, which is
the existing collection parameter for designating the field to route on within
the collection. It could be given the same name but maybe that would be
confusing? FWIW ElasticSearch has a "Rollover Index" API call with some
similarities to this feature... so maybe "rollover" might be the prefix? or
"partitioned"? I'm not sure I like these much; perhaps just "router.field" is
fine as-is. It's scoped to the alias.
That's it so far. Perhaps no {{TZ}} param needed at this juncture if the dates
are UTC... TZ will nonetheless be useful later in interpreting a "gap" to
create new partitions. It's also risky to have a TZ param that changes the
interpretation of the collection names since what if the TZ param is changed.
*Proposed collection naming convention:*
{{aliasname_yyyy-MM-dd_HH_mm_ss}}. Collection names have limitations (no
colons) so can't just use ISO8601. Because it's not IS08601, I figure don't
try to look too close to it -- thus no T separator. Furthermore it may be
abbreviated so that it does not have trailing zeros or symbols. Perhaps it
should nonetheless always end in a 'Z' so that there is no user
misunderstanding with the eventual addition of a {{TZ}} alias metadata?
> Add feature to DistributedURP to route time partitioned collections
> -------------------------------------------------------------------
>
> Key: SOLR-11542
> URL: https://issues.apache.org/jira/browse/SOLR-11542
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
> Fix For: 7.2
>
>
> Assuming we have some time partitioning metadata on an alias (see SOLR-11487
> for the metadata facility), we'll then need to route documents to the right
> collection. I tentatively propose a helper class to DistributedURP to do
> this. Perhaps a separate URP is plausible, though it will take some
> modifications to DistributedURP.
> The scope of this issue is:
> * decide on some alias metadata names & semantics
> * decide the collection suffix pattern. Read/write code (needed to route).
> * the routing code
> No new partition creation nor deletion happens is this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
