[
https://issues.apache.org/jira/browse/CASSANDRA-17017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511274#comment-17511274
]
Josh McKenzie commented on CASSANDRA-17017:
-------------------------------------------
generate.sh ran into the circle permissions outage yesterday (since jobs didn't
auto start I got blocked on their permissions issue starting them) so just did
it manually w/David's script + perl -pi -e to get around it.
JDK11 run is clean (i.e. the 2 known failures I'm seeing on other branches):
[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/188/workflows/ed4a8114-ed1c-4340-95cd-359b80b42127]
Anything else you need me to tweak [~bereng] or are we good to go?
> 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
> Fix For: 4.1
>
>
> 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.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
