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

Andres de la Peña edited comment on CASSANDRA-8720 at 5/5/23 9:25 AM:
----------------------------------------------------------------------

Thanks, patch 
[here|https://github.com/apache/cassandra/compare/trunk...adelapena:8720-trunk-hotfix].
 I'm running it [on 
Jenkins|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/2451/pipeline].
 It seems it has survived the build.


was (Author: adelapena):
Thanks, Patch 
[here|https://github.com/apache/cassandra/compare/trunk...adelapena:8720-trunk-hotfix],
 I'm running it [on 
Jenkins|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/2451/pipeline].
 It seems it has survived the build.

> 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: 5.0
>
>         Attachments: 8720.txt
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> 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]

Reply via email to