You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2014/09/18 19:40:34 UTC

[jira] [Resolved] (CASSANDRA-7971) Batches with > 100 statements should be logged as warnings.

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

Benedict resolved CASSANDRA-7971.
---------------------------------
    Resolution: Not a Problem

We already log if they are above a certain size (default 5K)

> Batches with > 100 statements should be logged as warnings.
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-7971
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7971
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Matt Stump
>
> Despite our documentation stating that batches are not to be used for bulk loading it's common for customers to attempt otherwise. They then go to production and encounter issues. I encounter 2-3 customers per week that run into this issue.
> I can't think of any reason why a logical transaction should span more than 100 rows so it seems like a good limit. Maybe make it a hidden configuration variable where 0 means disable all warnings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)