[
https://issues.apache.org/jira/browse/CASSANDRA-11099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137298#comment-15137298
]
Chris Bannister commented on CASSANDRA-11099:
---------------------------------------------
I realised when I started looking into the returned metadata that is not as
simple as I had thought. I would be great to have fixed for protocol 5 though.
Another option to mitigate is that if a client requests skip_metadata for a CAS
statement Cassandra should ignore it and return the result metadata, this
shouldn't be breaking.
> Prepared metadata does not include CAS applied column
> -----------------------------------------------------
>
> Key: CASSANDRA-11099
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11099
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Chris Bannister
> Priority: Minor
> 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)
