You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/05/14 16:27:00 UTC

[jira] [Reopened] (CASSANDRA-8930) Add a warn notification for clients

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

Aleksey Yeschenko reopened CASSANDRA-8930:
------------------------------------------

> 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)