[
https://issues.apache.org/jira/browse/CASSANDRA-17017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424146#comment-17424146
]
Josh McKenzie commented on CASSANDRA-17017:
-------------------------------------------
[~bereng]: consider me corrected and educated.
Pushed a commit w/updated support for the standalone verifier + updates to all
the StandaloneVerifierTest entries to make use of the new required argument. I
went so far as to make it one of the root required 3 and more extensively
documented the usage.
I suppose our one outlier with this right now is that nodetool verify doesn't
include quite as robust messaging about why you should be wary of verification
as does standalone verifier. Not sure I have an opinion on that disjoint.
Let me know what you think.
> Add required -f / --force option to nodetool verify
> ---------------------------------------------------
>
> Key: CASSANDRA-17017
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17017
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
>
> nodetool verify has some pretty significant problems with it (see
> CASSANDRA-9947).
> Until such time as we do the heavy(er) lift to fix the command, we should
> make it harder for people to shoot themselves in the foot with it. Adding a
> required "-f" flag to it with a requisite "Do you really know what you're
> doing? Check out this JIRA first" seems like it'd be the right thing to do in
> the interim.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
