[jira] [Commented] (CASSANDRA-17789) Extend nodetool verify with functionality to detect partitions with duplicate keys

["Josh McKenzie (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-17789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573887#comment-17573887 ] 

Josh McKenzie commented on CASSANDRA-17789:
-------------------------------------------

||Item|Link||
|PR|[link|https://github.com/apache/cassandra/pull/1765]|
|JDK8 CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/258/workflows/a07d3c10-e603-440c-b541-0ba08a633718]|
|JDK11 CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/258/workflows/1e218ad7-894a-4f3e-b117-f9b6cbb99d0a]|

Since this a trivial logging change on duplicate rows found no new testing introduced.

> Extend nodetool verify with functionality to detect partitions with duplicate keys
> ----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17789
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17789
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tool/nodetool
>            Reporter: Josh McKenzie
>            Assignee: Josh McKenzie
>            Priority: Normal
>
> We've seen instances where, during upgrades across major versions and in mixed version clusters, we end up with data in a table that has duplication of primary keys. This is obviously an illegal state and being able to quickly scan for this and log partition keys for which we're seeing this state has proven quite useful.
> It's a fairly small change to verify/scrub to integrate this extra functionality.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org