[
https://issues.apache.org/jira/browse/SOLR-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242236#comment-16242236
]
David Smiley commented on SOLR-11487:
-------------------------------------
Decomposing aliases.json has pros/cons, but it won't remove the possibility of
races between modifying some portion of the aliases state; it just makes it
more rare. So we still need to deal with races in code.... using a zkVersion
with a retry and eventual timeout, etc.
Good observation in "Map Conversion"; there is no perfect choice. I suppose
"complicated serialization" needn't be too bad? This would mean that a
user-provided comma separated list might end up normalized according to the
rules of StrUtils.splitSmart and reversed as StrUtils.join and that's probably
okay. So if a user strangely supplies "\f\o\o" it will see "foo" back.
I could take a stab at ZkStateReader loop/retry, and removing the
Aliases.priorChange stuff. I don't argue what you have now doesn't work, only
that the particular arrangement is unclear.
> 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_11487.patch, SOLR_11487.patch,
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
