[
https://issues.apache.org/jira/browse/CASSANDRA-14596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16560834#comment-16560834
]
Jay Zhuang commented on CASSANDRA-14596:
----------------------------------------
The problem is because the
[{{result_metadata_id}}|https://github.com/apache/cassandra/blob/trunk/doc/native_protocol_v5.spec#L414]
is introduced in protocol V5 but not included in 3.11 branch: CASSANDRA-10786.
It's a backward incompatible change (which I think is fine for a beta
protocol). So the [newer driver is trying to
read|https://github.com/datastax/python-driver/blob/master/cassandra/protocol.py#L679]
the {{result_metadata_id}}, which causes failure to parse prepare statement
response.
It's impacting the customer who is:
1. Using 3.11 and
2. Using V5 protocol (Beta) and
3. Newer driver after CASSANDRA-10786
Here are a few solutions I can think of:
1. backport the feature to 3.11;
2. add a dummy {{result_metadata_id}} in the prepare statement response just to
make it compatible with the latest v5 protocol, so we don't have to backport
the full feature (may have other consequence);
3. Disable the test and only run it for 4.0. For the customer using 3.11 + V5
protocol, they have to use the older driver before CASSANDRA-10786.
cc. [~ifesdjeen]
> [dtest] test_mutation_v5 - write_failures_test.TestWriteFailures
> ----------------------------------------------------------------
>
> Key: CASSANDRA-14596
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14596
> Project: Cassandra
> Issue Type: Bug
> Components: Testing
> Reporter: Jason Brown
> Priority: Minor
> Labels: dtest
>
> dtest fails with the following pytest error:
> {noformat}
> s = b'\x00\x00'
> > unpack = lambda s: packer.unpack(s)[0]
> E struct.error: unpack requires a buffer of 4 bytes
> {noformat}
> Test fails on 3.11 (was introduced for 3.10), but succeeds on trunk
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
