[pulsar-admin] New option takes precedence over deprecated option #12260
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, we use new option to replace some deprecated option in
client-tools. for example:pulsar/pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/CmdSources.java
Lines 141 to 144 in 9d30914
In order to maintain compatibility, the deprecated option still take effect through merging, as below:
pulsar/pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/CmdSources.java
Lines 183 to 191 in 9d30914
But I found that its priority is higher than the new option, which causes the new option to be invalid when we set both at the same time.
Modifications
Adjust the priority of the new and deprecated option, the deprecated option only takes effect when the new option is not set.
Documentation