You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2026/07/11 16:56:00 UTC

[jira] [Commented] (CASSANDRA-21509) Enforcing uniqueness of paramLabel across command options

    [ https://issues.apache.org/jira/browse/CASSANDRA-21509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095604#comment-18095604 ] 

Maxim Muzafarov commented on CASSANDRA-21509:
---------------------------------------------

https://pre-ci.cassandra.apache.org/job/cassandra/625/

> 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
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Normal
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org