[
https://issues.apache.org/jira/browse/CASSANDRA-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351035#comment-14351035
]
Tyler Hobbs commented on CASSANDRA-8930:
----------------------------------------
I asked for something similar in the v3 protocol, and Sylvain responded
[here|https://issues.apache.org/jira/browse/CASSANDRA-6855?focusedCommentId=13957675&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13957675].
To summarize: it's not worth the overhead unless we have a concrete need for
it. If you have anything in mind, feel free to mention it.
> 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)
