Can you elaborate on “will be using zkcli.sh”? Does that mean maybe in the not
too distant future it won’t be used?
And in terms of the immediate future, okay to add bin/solr zk now, and zkcli.sh
might need to be removed in Solr 11?
> On Sep 14, 2023, at 2:11 PM, Houston Putman wrote:
>
>> H
> Houston, would that work for the Solr-operator? I would be happy to work
with you to migrate the Solr-operator from zkcli.sh to bin/solr zk…..
I'm not sure that the Solr Operator will be using zkcli.sh, but in general
the Solr Operator needs a 2 major version migration path. So if it supports
8
Thanks for going through this.
Yeah, the TL;DR; is that we make sure that everything zkcli does is in the
bin/solr zk command structure. Based on (somewhat painful) experience in
other parts of the CLI, I think that we leave zkcli alone, as is for 9.x with
no “improvements” to make life ea
> what commands that exist in zkcli are already covered with existing bin/solr
> zk subcommands, which maybe are no longer needed
To clarify - you're thinking of removing functionality from zkcli if
there's already an equivalent in "bin/solr zk"? Or the opposite?
I'm definitely rusty on this bi
Hi all, I wanted to tap the braintrust to see what commands that exist in zkcli
are already covered with existing bin/solr zk subcommands, which maybe are no
longer needed, and which need porting over in some fashion.
Looking at ZkCLITest.java, I see tests for:
testBootstrapWithChroot - This ap
