[
https://issues.apache.org/jira/browse/CASSANDRA-13532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150381#comment-16150381
]
Michael Sear commented on CASSANDRA-13532:
------------------------------------------
I just came across this bug myself. I think, though, that it would be
preferable to fix the parser so it consumes a single value per argument. e.g. :
{code:java}
sstabledump -k mykey1 -k mykey2 mysstable
{code}
Don't you think? I'd have thought this would be more consistent with the way
arguments are normally used on the command line.
> sstabledump reports incorrect usage for argument order
> ------------------------------------------------------
>
> Key: CASSANDRA-13532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13532
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Ian Ilsley
> Assignee: Varun Barala
> Priority: Minor
> Labels: lhf
> Fix For: 3.0.15, 3.11.1, 4.0
>
> Attachments: sstabledump#printUsage.patch
>
>
> sstabledump usage reports
> {{usage: sstabledump <options> <sstable file path>}}
> However the actual usage is
> {{sstabledump <sstable file path> <options>}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
