You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Erick Ramirez (Jira)" <ji...@apache.org> on 2021/08/10 23:34:00 UTC
[jira] [Commented] (CASSANDRA-8720) Provide tools for finding wide
row/partition keys
[ https://issues.apache.org/jira/browse/CASSANDRA-8720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396940#comment-17396940 ]
Erick Ramirez commented on CASSANDRA-8720:
------------------------------------------
[~adelapena] & [~edimitrova], it would be really good to resurrect this ticket and target for 3.11 + 4.0 if we can. (y)
> 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
> Priority: Normal
> Fix For: 2.1.x, 2.2.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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org