-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep topic-level policies commands consistent with that for namespace… #9215
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good me, just left some minor comments. Since this is only breaking the CLI, I think it's not a serious problem.
pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/CmdTopics.java
Outdated
Show resolved
Hide resolved
pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/CmdTopics.java
Outdated
Show resolved
Hide resolved
pulsar-client-tools-test/src/test/java/org/apache/pulsar/admin/cli/PulsarAdminToolTest.java
Show resolved
Hide resolved
pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/CmdTopics.java
Outdated
Show resolved
Hide resolved
@315157973 Thank you for your contribution. Have we taken compatibilities into consideration in this PR? @sijia-w could you also help review this PR? Thank you. |
Regarding compatibility, I have discussed with @codelipenghui, considering that CLI is always input by humans (either by looking at the document to copy and paste, or through the help command), direct modification does not have a big impact. |
@315157973 Thank you for your clarification. Do not merge it before any eng approves it. |
/pulsarbot run-failure-checks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@315157973 @codelipenghui If the commands of topic level polices were introduced in any major releases, we should keep the backward compatibility. You can add the new commands and mark the old commands as deprecated and hidden.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
/pulsarbot run-failure-checks |
1 similar comment
/pulsarbot run-failure-checks |
@sijie It has been modified as required, please help CR again |
#9215) Fixes #9205 In #9108, we add some topic-level policies commands, and found some commands are not consistent with that for namespace-level. For example, On namespace-level, the policies commands are: ``` get-max-producers set-max-producers remove-max-producers get-max-unacked-messages-per-subscription set-max-unacked-messages-per-subscription remove-max-unacked-messages-per-subscription ``` On topic-level, the polices commands are: ``` get-maxProducers set-maxProducers remove-maxProducers get-max-unacked-messages-on-subscription set-max-unacked-messages-on-subscription remove-max-unacked-messages-on-subscription ``` Keep topic-level policies commands consistent with that for namespace (cherry picked from commit d557e0a)
Fixes #9205
Motivation
In #9108, we add some topic-level policies commands, and found some commands are not consistent with that for namespace-level.
For example,
On namespace-level, the policies commands are:
On topic-level, the polices commands are:
Modifications
Keep topic-level policies commands consistent with that for namespace
Verifying this change