lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gus Heck (JIRA)" <>
Subject [jira] [Commented] (SOLR-11487) Collection Alias metadata for time partitioned collections
Date Sun, 15 Oct 2017 17:30:00 GMT


Gus Heck commented on SOLR-11487:

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:
>             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

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

View raw message