[jira] [Updated] (SOLR-11487) Collection Alias metadata for time partitioned collections

["Gus Heck (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gus Heck updated SOLR-11487:
----------------------------
    Attachment: SOLR_11487.patch

Patch showing rough sketch of what I am thinking, The thing I like about this is it allows us to track metadata on the aliases, and the collections that they alias as well, which may be useful in caching info used in 11299, such as the calculated milliseconds that represent when a partition's data starts.

The thing I don't like about this is it does a lot of reading from Zk... possibly something like this should become maintained by watches and not read every time... which also makes me learn further in the direction of my comment in code that the metadata should probably be <String,Object> not <String,String>... to let JSON parsing do all our conversions for primitives.

> 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
>         Attachments: SOLR_11487.patch
>
>
> 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