[
https://issues.apache.org/jira/browse/CASSANDRA-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Yeksigian updated CASSANDRA-8930:
--------------------------------------
Attachment: 8930-trunk-v2.txt
I've attached a patch which address the review comments except the last one.
Since getting the remote warnings will take more time and wanted to try to get
this into v4, the patch doesn't yet address the last point; v1 I'd be happy
with coordinator only warnings, and then figure out remote warnings in a follow
up ticket.
> 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: 3.x
>
> Attachments: 8930-trunk-v2.txt, 8930-trunk.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)
