[
https://issues.apache.org/jira/browse/CASSANDRA-8720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-8720:
-----------------------------------------
Test and Documentation Plan:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/2303]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/2877/workflows/e683e442-fa86-4fe5-af6c-6a57665b3a93]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/2877/workflows/53f41727-77d8-494c-a2d1-ca4b1c71d4eb]|
Status: Patch Available (was: In Progress)
> Provide tools for finding wide row/partition keys
> -------------------------------------------------
>
> Key: CASSANDRA-8720
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8720
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Tools
> Reporter: J.B. Langston
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 3.11.x, 4.0.x
>
> Attachments: 8720.txt
>
>
> Multiple users have requested some sort of tool to help identify wide row
> keys. They get into a situation where they know a wide row/partition has been
> inserted and it's causing problems for them but they have no idea what the
> row key is in order to remove it.
> Maintaining the widest row key currently encountered and displaying it in
> cfstats would be one possible approach.
> Another would be an offline tool (possibly an enhancement to sstablekeys) to
> show the number of columns/bytes per key in each sstable. If a tool to
> aggregate the information at a CF-level could be provided that would be a
> bonus, but it shouldn't be too hard to write a script wrapper to aggregate
> them if not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
