You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gus Heck (JIRA)" <ji...@apache.org> on 2017/10/15 17:31:00 UTC
[jira] [Comment Edited] (SOLR-11487) Collection Alias metadata for
time partitioned collections
[ https://issues.apache.org/jira/browse/SOLR-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205218#comment-16205218 ]
Gus Heck edited comment on SOLR-11487 at 10/15/17 5:30 PM:
-----------------------------------------------------------
In zk nodes can have both values and children right? So the value of the node called aliases.json can remain the same json text, but it could also have a list of children corresponding to each alias and then each member of the alias containing that metadata... yes some duplication there, but this would mean that any older clients reading the value from the node will still get what they expect... newer code could simply ignore the old json...
was (Author: gus_heck):
In zk nodes can have both values and children right? So the value of the node called aliases.json can remain the same json text, but it could also have a list of children corresponding to each member of the alias containing that metadata... yes some duplication there, but this would mean that any older clients reading the value from the node will still get what they expect... newer code could simply ignore the old json...
> Collection Alias metadata for time partitioned collections
> ----------------------------------------------------------
>
> Key: SOLR-11487
> URL: https://issues.apache.org/jira/browse/SOLR-11487
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
>
> SOLR-11299 outlines an approach to using a collection Alias to refer to a series of collections of a time series. We'll need to store some metadata about these time series collections, such as which field of the document contains the timestamp to route on.
> The current {{/aliases.json}} is a Map with a key {{collection}} which is in turn a Map of alias name strings to a comma delimited list of the collections.
> _If we change the comma delimited list to be another Map to hold the existing list and more stuff, older CloudSolrClient (configured to talk to ZooKeeper) will break_. Although if it's configured with an HTTP Solr URL then it would not break. There's also some read/write hassle to worry about -- we may need to continue to read an aliases.json in the older format.
> Alternatively, we could add a new map entry to aliases.json, say, {{collection_metadata}} keyed by alias name?
> Perhaps another very different approach is to attach metadata to the configset in use?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org