Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1333031594.26071267595727228.JavaMail.jira@brutus.apache.org>
Date: Wed, 3 Mar 2010 05:55:27 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Updated: (CASSANDRA-843) Issue warnings for large rows
In-Reply-To: <267197711.16311267566447201.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-843:
---------------------------------------

    Attachment: 0001_remove_underscores_in_dd.patch

> Issue warnings for large rows
> -----------------------------
>
>                 Key: CASSANDRA-843
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-843
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.6
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 0.6
>
>         Attachments: 0001_remove_underscores_in_dd.patch, 0002_warn_on_large_rows.patch, 0003_key_exclusion_in_sste.patch
>
>
> 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.