Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 14 May 2015 13:20:00 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12780174.1425677113000.113682.1431609600177@Atlassian.JIRA>
In-Reply-To: <JIRA.12780174.1425677113000@Atlassian.JIRA>
References: <JIRA.12780174.1425677113000@Atlassian.JIRA>
 <JIRA.12780174.1425677113603@arcas>
Subject: [jira] [Updated] (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:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-8930:
-----------------------------------------
    Attachment: 8930-v3.txt

> 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
>            Assignee: Carl Yeksigian
>              Labels: client-impacting, protocolv4
>             Fix For: 2.2 beta 1
>
>         Attachments: 8930-trunk-v2.txt, 8930-trunk.txt, 8930-v3.txt
>
>
> 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)