[
https://issues.apache.org/jira/browse/CASSANDRA-21509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated CASSANDRA-21509:
----------------------------------------
Fix Version/s: 6.0-alpha2
7.0
(was: 7.x)
Source Control Link:
https://github.com/apache/cassandra/commit/7874fdae578d61a770792911aa833f6fa91856e4
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Merged to 6.0, trunk
Thank you for the review.
> Enforcing uniqueness of paramLabel across command options
> ---------------------------------------------------------
>
> Key: CASSANDRA-21509
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21509
> Project: Apache Cassandra
> Issue Type: Task
> Components: Tool/nodetool
> Reporter: Maxim Muzafarov
> Assignee: Maxim Muzafarov
> Priority: Normal
> Fix For: 6.0-alpha2, 7.0
>
>
> On trunk, paramLabel is display-only: duplicate labels cause no parsing or
> behavioral problem, only ambiguous help output which some time confuses a
> command usage.
> The uniqueness rule such as "paramLabels must be unique within a command
> across options, aliases, and positionals is a new convention this ticket
> introduces, not an existing invariant being violated. Its purpose is
> forward-looking: CEP-38 turns these labels into wire keys for cql commands.
> Enforcing the convention on trunk now means no new commands can introduce
> collisions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
