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/02/17 18:52:00 UTC
[jira] [Comment Edited] (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=17286080#comment-17286080 ]
Nazerke Seidan edited comment on SOLR-14341 at 2/17/21, 6:51 PM:
-----------------------------------------------------------------
Created a PR [https://github.com/apache/lucene-solr/pull/2391|https://github.com/apache/lucene-solr/pull/2391)] although many tests do fail now, working on that. I would like to get some reviews.
was (Author: nazerke):
Created a PR ([https://github.com/apache/lucene-solr/pull/2391)] although many tests do fail now, working on that. I would like to get some reviews.
> 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
>
> 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