[
https://issues.apache.org/jira/browse/CASSANDRA-8720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710030#comment-14710030
]
J.B. Langston commented on CASSANDRA-8720:
------------------------------------------
Looks like we crossed over each other's comments. I think if this offline tool
needs to go through the motions of compacting without actually writing out new
files or deleting the old ones, then that would be fine. Of course it would
require lots of I/O and people would need to be aware of that, but in some
cases I think they'd be willing to accept that in order to identify large
partitions.
> 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
> Reporter: J.B. Langston
>
> 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
(v6.3.4#6332)
