Jacek Lewandowski created CASSANDRA-17072:
---------------------------------------------
Summary: Fix client warning in schema change related statements
Key: CASSANDRA-17072
URL: https://issues.apache.org/jira/browse/CASSANDRA-17072
Project: Cassandra
Issue Type: Bug
Components: Local/Other
Reporter: Jacek Lewandowski
Assignee: Jacek Lewandowski
Extracted this as a separate ticket per discussion on CASSANDRA-17044
This seemed to be screwed a bit. In just two schema alteration statements we
collect client warnings which are captured during the transformation into a
local collection.
I guess it is done that way because the transformation is being executed in a
different stage (migration) and client warnings collected in that stage are not
present in the stage where the query is executed.
Then, the client warnings are retrieved using {{clientWarnings}} method and
added to the captured client warnings in the stage which is executing the
query.
This mechanism was implemented only in two schema alteration statements. It is
possible that for other ones the client warnings can simply get lost.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
