[
https://issues.apache.org/jira/browse/SOLR-14341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366950#comment-17366950
]
David Smiley commented on SOLR-14341:
-------------------------------------
In Solr 8.10, we should also have ZkStateReader.readConfigName check the
DocCollection (state.json) if the old location doesn't have the configSet name.
For another JIRA issue.
Any way, I think the PR here is ready to merge. Basic compatibility with Solr 8
was tested by creating a Solr 8 collection, shutting down, then run with Solr
9. The Solr 9 transition implicitly led to the state.json files containing the
config name because of state updates that otherwise had to be made when a
replica changes its state. SolrJ 8 CloudSolrClient wasn't tested but we didn't
see any real dependencies in there on this. The old location is still updated
to help with compatibility but it isn't read by Solr 9 except for when it's not
in the new location. I plan to merge this Thursday.
> 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: 3.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: [email protected]
For additional commands, e-mail: [email protected]
