[ 
https://issues.apache.org/jira/browse/SOLR-14115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842379#comment-17842379
 ] 

ASF subversion and git services commented on SOLR-14115:
--------------------------------------------------------

Commit b530aa53e1e13deeb0fa99b7e58924de60317555 in solr's branch 
refs/heads/main from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=b530aa53e1e ]

SOLR-14115: Update the docs to reference to the bin/solr equivalent of the 
zkcli.sh (#2428)

Didn't eliminate zookeeper-utilities.adoc as there may be an option to break up 
the solr-control-script-reference.adoc that became apparent in this commit, 
however saving for another day.

> Deprecate zkcli.sh
> ------------------
>
>                 Key: SOLR-14115
>                 URL: https://issues.apache.org/jira/browse/SOLR-14115
>             Project: Solr
>          Issue Type: Improvement
>          Components: scripts and tools
>            Reporter: Erick Erickson
>            Assignee: Eric Pugh
>            Priority: Major
>             Fix For: 9.7
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> I think it's a valid argument that these have outlived their usefulness and 
> we should remove them and have APIs to do what Solr requires. Especially if 
> we can find and point to a third-party visual ZK tool for _changing_ 
> arbitrary data in ZK. Zookeeper 3.5.5 has the admin server which has a UI 
> (although I don't see how to change data in ZK with it. Haven't looked very 
> much).
> While we're ripping stuff out of Solr, are these candidates? It would break 
> my heart to rip ZK support out from bin/solr, but all good things must come 
> to an end. Why do we maintain three (zkcli, bin/solr and the APIs) ways of 
> doing the same thing?
> Mark put the zkcli stuff in before we had APIs to do what Solr needs to do 
> with ZK, mainly uploading configsets at the time. I put the zk support in 
> bin/solr also before the APIs existed because I thought having to learn our 
> custom wrapper for ZK was yet another orphan bit of code laying around. All 
> before we had things like the configsets API.
> Personally, I'd prefer removing zkcli rather than bin/solr, but that's 
> because I originated the bin/solr code ;)
> This occurred when reading SOLR-14109, I'm not entirely sure what I _really_ 
> think about it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to