[jira] [Commented] (CASSANDRA-11099) Prepared metadata does not include CAS applied column

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-11099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136762#comment-15136762 ] 

Sylvain Lebresne commented on CASSANDRA-11099:
----------------------------------------------

The problem is that the result set of a CAS statement is not stable across execution: if the write succeed then it will only contain the {{[applied]}} column, but if it doesn't apply, it will also return the columns on which their was conditions. In other words, we can't do that currently.

Now, I suppose we could change how we do that and always return the same resultSet, with both {{[applied]}} and the columns having conditions, but return {{null}} for those columns if {{[applied] == true}}, but that's strictly speaking a breaking change and so at best we should do that in the next version of the protocol. So marking the ticket accordingly.

> Prepared metadata does not include CAS applied column
> -----------------------------------------------------
>
>                 Key: CASSANDRA-11099
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11099
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Chris Bannister
>              Labels: protocolv5
>
> When executing a CAS statement the first column is the [applied] boolean column indicating success, but when preparing it does get returned. This means that clients can not cache the prepared statement result metadata to use instead of the execute metadata.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)