[
https://issues.apache.org/jira/browse/CASSANDRA-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711982#comment-16711982
]
Stefan Podkowinski commented on CASSANDRA-14921:
------------------------------------------------
Can't we just downgrade to 0.9.3 in dtest's requirements.txt? If there's a
compatibility issue with our tests and 0.10, shouldn't we either use a
different thrift version, or fix the issue on our side (which your patch does)?
> thrift_test.py failures on 3.0 and 3.x branches
> -----------------------------------------------
>
> Key: CASSANDRA-14921
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14921
> Project: Cassandra
> Issue Type: Bug
> Components: Testing
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Major
> Fix For: 3.0.x, 3.11.x
>
>
> {{putget_test::TestPutGet::test_wide_slice}} fails on CircleCI since the
> docker image was updated for CASSANDRA-14713. The reason for this is that the
> {{fastbinary}} extension used by {{TBinaryProtocolAccelerated}} is not
> compatible with thrift 0.10.0 (according to [this bug report against
> Pycassa|https://github.com/pycassa/pycassa/issues/245]). The offending binary
> is present in the filesystem of the [current docker
> image|https://hub.docker.com/r/spod/cassandra-testing-ubuntu18-java11/], but
> wasn't in [the previous image
> |https://hub.docker.com/r/kjellman/cassandra-test/], which meant that thrift
> would fallback to the standard protocol implementation (silently).
> As this is the only test which uses {{TBinaryProtocolAccelerated}} it's easy
> enough to switch it to {{TBinaryProtocol}}, which also fixes things. We might
> want consider removing the binary next time the image is updated though (cc
> [[email protected]]).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
