[
https://issues.apache.org/jira/browse/SOLR-14341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18068376#comment-18068376
]
ASF subversion and git services commented on SOLR-14341:
--------------------------------------------------------
Commit bfda10e9519c33aa5fb4a4611da4131e2cf4fb43 in solr's branch
refs/heads/branch_10x from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=bfda10e9519 ]
SOLR-18166: Remove 'linkconfig' tool and related code (#4232)
"Linkconfig" is a functionality initially added prior to our
collection-admin APIs, when users needed to run manual commands to
associate or "link" a new collection with a particular config by storing
the config name on the /collections/<collName> node.
Storing config information in this location was deprecated in SOLR-14341
and can be removed now that 10.0 is out the door. This commit removes
several methods that checked for config info at this location, as well
as the "linkconfig" that was user's primary way of storing this
information in the past.
> 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
> Fix For: 9.0
>
> Time Spent: 4h
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]