[
https://issues.apache.org/jira/browse/CASSGO-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039407#comment-18039407
]
Bohdan Siryk commented on CASSGO-98:
------------------------------------
{quote}I believe that's not enough because that flag is actually what's checked
to see if the segment needs to be compressed\{quote}
I really didn't find any other usages of this flag except the one I described
in the above message.
Anyway, I prepared a patch that fixes the described issue. I'm unsure if we
need to write an integration test for this, and if so, what it should look like.
[~joaoreis] Could you please review this one once you have a chance?
[https://github.com/apache/cassandra-gocql-driver/pull/1917]
> Frame compression header is being set with v5
> ---------------------------------------------
>
> Key: CASSGO-98
> URL: https://issues.apache.org/jira/browse/CASSGO-98
> Project: Apache Cassandra Go driver
> Issue Type: Bug
> Components: Core
> Reporter: João Reis
> Assignee: Bohdan Siryk
> Priority: Normal
> Fix For: 2.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In protocol v5 the frame (v5 envelope) compression header flag should be
> ignored because compression happens at segment (v5 frame) level. The frame
> body itself is not compressed so this is a bug.
> This was found when trying to connect to
> [ZDM-Proxy|https://github.com/datastax/zdm-proxy/] but connecting to a C*
> 5.0.x cluster works fine (I assume C* is ignoring this flag completely when
> it's a v5 frame).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
