[
https://issues.apache.org/jira/browse/CASSANDRA-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840356#action_12840356
]
Brandon Williams edited comment on CASSANDRA-843 at 3/2/10 10:21 PM:
---------------------------------------------------------------------
Also, it would be cool if you could skip certain keys with sstable2json so that
there is an avenue for removing the problem row in the pathological case where
you can't possibly allocate enough memory to get it removed by compaction.
was (Author: brandon.williams):
Also, it would be cool if you could skip certain keys with sstable2json so
that there is an avenue for removing the problem row in the pathological case
where you can't possible allocate enough memory to get it removed by compaction.
> Issue warnings for large rows
> -----------------------------
>
> Key: CASSANDRA-843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-843
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 0.6
>
>
> If you make a very fat row, eventually CASSANDRA-16 will bite you. For 0.7
> this will get resolved, but for 0.6 it would be nice if this were easier to
> diagnose via a user-defined threshold in MB that, when exceeded, would issue
> a warning with the row key name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
