[ https://issues.apache.org/jira/browse/CASSANDRA-8720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397275#comment-17397275 ]
Andres de la Peña commented on CASSANDRA-8720: ---------------------------------------------- CASSANDRA-16310 will add tracking of the top partitions, which can be queried online and doesn't require to scan the data. The idea here is having an offline tool like [{{sstablepartitions}}|https://docs.datastax.com/en/dse/6.7/dse-dev/datastax_enterprise/tools/toolsSStables/sstablepartitions.html] allowing more ad-hoc queries, such as getting all the partitions over a certain threshold. > 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.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org