Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 6 Mar 2015 22:38:39 +0000 (UTC)
From: "Robert Stupp (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12780174.1425677113000.25548.1425681519679@Atlassian.JIRA>
In-Reply-To: <JIRA.12780174.1425677113000@Atlassian.JIRA>
References: <JIRA.12780174.1425677113000@Atlassian.JIRA>
 <JIRA.12780174.1425677113603@arcas>
Subject: [jira] [Commented] (CASSANDRA-8930) Add a warn notification for
 clients
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Stupp commented on CASSANDRA-8930:
-----------------------------------------

If the warning is just for "too big batches", it could be handled more efficiently on the driver side.
E.g. by enabling some "fail/log on batches larger than X bytes" on the driver's {{Session}} object. It could be turned on during development and testing - and disabled in production.

> Add a warn notification for clients
> -----------------------------------
>
>                 Key: CASSANDRA-8930
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8930
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Carl Yeksigian
>              Labels: protocolv4
>             Fix For: 3.0
>
>
> Currently, if a query generates a warning, it is going to be logged server side. If the person writing the query is not the admin, that warning isn't going to have an impact on the query, and we're just going to fill up the server logs.
> We should push these warnings back to the client so the driver users can make necessary changes.


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