[
https://issues.apache.org/jira/browse/SOLR-18166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18068310#comment-18068310
]
ASF subversion and git services commented on SOLR-18166:
--------------------------------------------------------
Commit ebe71e48f033d79d001d0ba9474e9e0e060a3cd7 in solr's branch
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=ebe71e48f03 ]
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.
> Remove outmoded "bin/solr zk linkconfig" subcommand and related code
> --------------------------------------------------------------------
>
> Key: SOLR-18166
> URL: https://issues.apache.org/jira/browse/SOLR-18166
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
> Affects Versions: main(11.0)
> Reporter: Jason Gerlowski
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> SOLR-3460 added the "zkcli.sh" script that we shipped with Solr distributions
> for many releases. This tool contained a subcommand, "linkconfig", that
> created a zkNode at the path "/collections/<someCollName>" whose
> contents/data was essentially the configset name.
> This is something that made sense back in the 2012 timeframe when it was
> added. At that time most of the "Collection Admin" or collection CRUD APIs
> we know and love today didn't exist. So this manual "linking" process was a
> required part of creating a new collection.
> But today this code is purely vestigial. There are no usecases that would
> have a user link a config today. And no code in Solr looks for the
> "configName" property at this outmoded location, excepting a few deprecated
> methods that are slated for removal in or after Solr 10.
> I propose in this ticket that we:
> * remove "bin/solr zk linkconfig" (the linkconfig tooling was migrated here
> when zkcli.sh was sunset as a part of SOLR-14115)
> * remove all of the methods and call-sites previously deprecated by
> SOLR-14341
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
