[
https://issues.apache.org/jira/browse/HDDS-13486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-13486:
----------------------------------
Labels: pull-request-available (was: )
> Enforce Exclusivity Between Node Selection and Sorting Options in
> ListInfoSubcommand
> ------------------------------------------------------------------------------------
>
> Key: HDDS-13486
> URL: https://issues.apache.org/jira/browse/HDDS-13486
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sreeja
> Assignee: Sreeja
> Priority: Major
> Labels: pull-request-available
>
> Currently, the ozone admin datanode list command allows users to combine node
> selection options (e.g., --node-id, --ip, --hostname) with usage sorting
> options (e.g., --most-used, --least-used).
> This combination leads to confusing command behavior. For instance,
> {code:java}
> ozone admin datanode list --most-used=true --node-id=<dn-id>{code}
> will attempt filter to a single specified node and then to sort by usage.
> This provides a misleading output to the user.
> To improve command clarity and user experience, we need to make node
> selection options and usage sorting options mutually exclusive. This means a
> user will only be able to specify options for either selecting specific nodes
> or sorting the entire list by usage, but not both simultaneously. This
> ensures the command's intent is clear and its output is intuitive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
