[jira] [Updated] (CASSANDRA-20790) Move --print-port option in the nodetool commands from global to command-specific
[ https://issues.apache.org/jira/browse/CASSANDRA-20790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-20790: Epic Link: CASSANDRA-21277 Labels: CEP-38 (was: ) > Move --print-port option in the nodetool commands from global to > command-specific > - > > Key: CASSANDRA-20790 > URL: https://issues.apache.org/jira/browse/CASSANDRA-20790 > Project: Apache Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Labels: CEP-38 > Fix For: 6.0-alpha1, 6.0 > > > The --print-port option is currently defined as a global option in the > nodetool hierarchy, but is only used by a small subset of commands (~9 out of > 100+). This creates unnecessary complexity in the global command hierarchy > view and should be refactored to be command-specific while maintaining > backward compatibility. > h3. Proposed Solution > # Remove --print-port from global options in NodetoolCommand > # Add --print-port option to each command that needs it > # Maintain backward compatibility by ensuring both syntaxes supported: > ./nodetool --print-port subcommand (current) > ./nodetool subcommand --print-port (new) > # Update direct access patterns to use the local option -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-20790) Move --print-port option in the nodetool commands from global to command-specific
[ https://issues.apache.org/jira/browse/CASSANDRA-20790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-20790: Fix Version/s: 5.1 (was: 5.x) Source Control Link: https://github.com/apache/cassandra/commit/c9fe399b06d3ab30f1ca4db6e6c0bdd26a64e8f7 Resolution: Fixed Status: Resolved (was: Ready to Commit) [~smiklosovic] thank you for review! Committed to the trunk. > Move --print-port option in the nodetool commands from global to > command-specific > - > > Key: CASSANDRA-20790 > URL: https://issues.apache.org/jira/browse/CASSANDRA-20790 > Project: Apache Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.1 > > > The --print-port option is currently defined as a global option in the > nodetool hierarchy, but is only used by a small subset of commands (~9 out of > 100+). This creates unnecessary complexity in the global command hierarchy > view and should be refactored to be command-specific while maintaining > backward compatibility. > h3. Proposed Solution > # Remove --print-port from global options in NodetoolCommand > # Add --print-port option to each command that needs it > # Maintain backward compatibility by ensuring both syntaxes supported: > ./nodetool --print-port subcommand (current) > ./nodetool subcommand --print-port (new) > # Update direct access patterns to use the local option -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-20790) Move --print-port option in the nodetool commands from global to command-specific
[ https://issues.apache.org/jira/browse/CASSANDRA-20790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-20790: Reviewers: Stefan Miklosovic Status: Review In Progress (was: Patch Available) > Move --print-port option in the nodetool commands from global to > command-specific > - > > Key: CASSANDRA-20790 > URL: https://issues.apache.org/jira/browse/CASSANDRA-20790 > Project: Apache Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > > The --print-port option is currently defined as a global option in the > nodetool hierarchy, but is only used by a small subset of commands (~9 out of > 100+). This creates unnecessary complexity in the global command hierarchy > view and should be refactored to be command-specific while maintaining > backward compatibility. > h3. Proposed Solution > # Remove --print-port from global options in NodetoolCommand > # Add --print-port option to each command that needs it > # Maintain backward compatibility by ensuring both syntaxes supported: > ./nodetool --print-port subcommand (current) > ./nodetool subcommand --print-port (new) > # Update direct access patterns to use the local option -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-20790) Move --print-port option in the nodetool commands from global to command-specific
[ https://issues.apache.org/jira/browse/CASSANDRA-20790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-20790: Status: Ready to Commit (was: Review In Progress) > Move --print-port option in the nodetool commands from global to > command-specific > - > > Key: CASSANDRA-20790 > URL: https://issues.apache.org/jira/browse/CASSANDRA-20790 > Project: Apache Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > > The --print-port option is currently defined as a global option in the > nodetool hierarchy, but is only used by a small subset of commands (~9 out of > 100+). This creates unnecessary complexity in the global command hierarchy > view and should be refactored to be command-specific while maintaining > backward compatibility. > h3. Proposed Solution > # Remove --print-port from global options in NodetoolCommand > # Add --print-port option to each command that needs it > # Maintain backward compatibility by ensuring both syntaxes supported: > ./nodetool --print-port subcommand (current) > ./nodetool subcommand --print-port (new) > # Update direct access patterns to use the local option -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-20790) Move --print-port option in the nodetool commands from global to command-specific
[ https://issues.apache.org/jira/browse/CASSANDRA-20790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-20790: Description: The --print-port option is currently defined as a global option in the nodetool hierarchy, but is only used by a small subset of commands (~9 out of 100+). This creates unnecessary complexity in the global command hierarchy view and should be refactored to be command-specific while maintaining backward compatibility. h3. Proposed Solution # Remove --print-port from global options in NodetoolCommand # Add --print-port option to each command that needs it # Maintain backward compatibility by ensuring both syntaxes supported: ./nodetool --print-port subcommand (current) ./nodetool subcommand --print-port (new) # Update direct access patterns to use the local option was: The --print-port option is currently defined as a global option in the nodetool hierarchy, but is only used by a small subset of commands (~9 out of 100+). This creates unnecessary complexity in the global command hierarchy view and should be refactored to be command-specific while maintaining backward compatibility. h3. Proposed Solution # Remove --print-port from global options in NodetoolCommand # Add --print-port option to each command that needs it # Maintain backward compatibility by ensuring both syntaxes supported: ./nodetool --print-port subcommand (current) ./nodetool subcommand --print-port (new) # Update direct access patterns (like in RemoveNode.Status) to use the local option > Move --print-port option in the nodetool commands from global to > command-specific > - > > Key: CASSANDRA-20790 > URL: https://issues.apache.org/jira/browse/CASSANDRA-20790 > Project: Apache Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > > The --print-port option is currently defined as a global option in the > nodetool hierarchy, but is only used by a small subset of commands (~9 out of > 100+). This creates unnecessary complexity in the global command hierarchy > view and should be refactored to be command-specific while maintaining > backward compatibility. > h3. Proposed Solution > # Remove --print-port from global options in NodetoolCommand > # Add --print-port option to each command that needs it > # Maintain backward compatibility by ensuring both syntaxes supported: > ./nodetool --print-port subcommand (current) > ./nodetool subcommand --print-port (new) > # Update direct access patterns to use the local option -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-20790) Move --print-port option in the nodetool commands from global to command-specific
[ https://issues.apache.org/jira/browse/CASSANDRA-20790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated CASSANDRA-20790: Summary: Move --print-port option in the nodetool commands from global to command-specific (was: Refactor --print-port option in the nodetool commands from global to command-specific) > Move --print-port option in the nodetool commands from global to > command-specific > - > > Key: CASSANDRA-20790 > URL: https://issues.apache.org/jira/browse/CASSANDRA-20790 > Project: Apache Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Normal > Fix For: 5.x > > > The --print-port option is currently defined as a global option in the > nodetool hierarchy, but is only used by a small subset of commands (~9 out of > 100+). This creates unnecessary complexity in the global command hierarchy > view and should be refactored to be command-specific while maintaining > backward compatibility. > h3. Proposed Solution > # Remove --print-port from global options in NodetoolCommand > # Add --print-port option to each command that needs it > # Maintain backward compatibility by ensuring both syntaxes supported: > ./nodetool --print-port subcommand (current) > ./nodetool subcommand --print-port (new) > # Update direct access patterns (like in RemoveNode.Status) to use the local > option -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
