You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Nazerke Seidan (Jira)" <ji...@apache.org> on 2021/03/10 17:42:00 UTC
[jira] [Commented] (SOLR-14341) Move a collection's configSet name
to state.json
[ https://issues.apache.org/jira/browse/SOLR-14341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299009#comment-17299009 ]
Nazerke Seidan commented on SOLR-14341:
---------------------------------------
I have written some stuff in this doc [https://docs.google.com/document/d/1I9eKlmRXs6aGYCAyZ9Ih956ukC74YUbGpV-WOhkyKIk/edit?usp=sharing] in order to get some inputs from you in particular backward compatibility concern.
[~janhoy], [~houston], [~noble.paul] mentioning you as you are a watcher and you might have some ideas, thanks.
> Move a collection's configSet name to state.json
> ------------------------------------------------
>
> Key: SOLR-14341
> URL: https://issues.apache.org/jira/browse/SOLR-14341
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It's a bit odd that a collection's state.json knows everything about a collection except for perhaps the most important pointer -- the configSet name. Presently the configSet name is retrieved via {{ZkStateReader.getConfigName(collectionName)}} which looks at the zk path {{/collections/collectionName}} (an intermediate node) interpreted as a trivial JSON object. Combining the configSet name into state.json is simpler and also more efficient since many calls to grab the configset name _already_ need the state.json (via a DocCollection object).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org