[
https://issues.apache.org/jira/browse/CASSANDRA-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543665#comment-14543665
]
Aleksey Yeschenko commented on CASSANDRA-8930:
----------------------------------------------
1. we've decided to not deprecate {{UNLOGGED}} batches just yet (see Jake's
comment in CASSANDRA-9283), so {{BatchStatement}} must remove that client
warning. Following that, the tests should be rewritten to use some other
warning (a batch size based one, or TO-based one).
2. Truncation logic hasn't been updated for multiple warnings/{{string list}}
format
I've attached a v3 with those addressed. Will commit if you are fine with the
(minor) changes in there (you being Carl).
> 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)
