[
https://issues.apache.org/jira/browse/CASSANDRA-17017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17017:
--------------------------------------
Test and Documentation Plan: Trivial revision of existing test; update of
option output on the tool pointing to JIRA.
Status: Patch Available (was: Open)
[PR|https://github.com/apache/cassandra/pull/1246]
Kicked off a slow burn of dtests on CI just in case any of them relied on
verify somehow and I'm not seeing it by grepping.
[JDK8|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/96/workflows/7686b1fb-267a-464c-8f49-6de00dc8baea]
[JDK11|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/96/workflows/8dbd2169-1147-4215-889e-3ef4071148d6]
> 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]
