[ 
https://issues.apache.org/jira/browse/CASSANDRA-13697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Brown updated CASSANDRA-13697:
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.11.3
                   3.0.17
                   4.0
           Status: Resolved  (was: Ready to Commit)

committed as sha {{3d7471a56b7a58b41047ff704ebe4b0a89bda6f9}}

I backported the patch as-is to 3.11. Further, I added the {{CAS}} entry to the 
spec docs in 3.0.

Thanks for the patch and the review!

> CDC and VIEW writeType missing from spec for write_timeout / write_failure
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-13697
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13697
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Documentation and Website
>            Reporter: Andy Tolbert
>            Assignee: Vinay Chella
>            Priority: Minor
>              Labels: lhf
>             Fix For: 4.0, 3.0.17, 3.11.3
>
>
> In cassandra 3.0 a new {{WriteType}} {{VIEW}} was added which appears to be 
> used when raising a {{WriteTimeoutException}} when the local view lock for a 
> key cannot be acquired within timeout.
> In cassandra 3.8 {{CDC}} {{WriteType}} was added for when 
> {{cdc_total_space_in_mb}} is exceeded when doing a write to data tracked by 
> cdc.
> The [v4 
> spec|https://github.com/apache/cassandra/blob/cassandra-3.11.0/doc/native_protocol_v4.spec#L1051-L1066]
>  currently doesn't cover these two write types.   While the protocol allows 
> for a free form string for write type, it would be nice to document that 
> types are available since some drivers (java, cpp, python) attempt to 
> deserialize write type into an enum and may not handle it well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to