[
https://issues.apache.org/jira/browse/SOLR-17586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903676#comment-17903676
]
Jan Høydahl commented on SOLR-17586:
------------------------------------
Testing the fix I also discovered that the tool also prints deprecation
warnings from CommonsCli to stdout
{code:java}
./server/scripts/cloud-scripts/zkcli.sh -zkhost localhost:9983 -cmd get
/security.json 2>/dev/null
Option 'zkhost': Deprecated for removal since 9.7: Use --zk-host instead
Option 'zkhost': Deprecated for removal since 9.7: Use --zk-host instead
{} {code}
This seems harder to fix if it is printed by commons CLI itself?
> Deprecation of zkcli.sh broke solr operator
> -------------------------------------------
>
> Key: SOLR-17586
> URL: https://issues.apache.org/jira/browse/SOLR-17586
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: 9.7
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 9.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In SOLR-14115 we deprecated zkcli.sh. A deprecation echo was added to the
> script in 9.x and it was removed in 10.0.
> Turns out the deprecation message is always printed (stdout) thus breaking
> scripts that rely on capturing the output from the script when used with
> {{{}-cmd get{}}}.
> This can be fixed by echoing to stderr instead with
> {code:bash}
> >&2 echo "foo"
> {code}
--
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
