[
https://issues.apache.org/jira/browse/CASSGO-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039416#comment-18039416
]
Bohdan Siryk commented on CASSGO-98:
------------------------------------
Thanks!
{quote}
I saw
if f.compres != nil
and assumed this was associated with the compression flag
{quote}
I see. Yeah, that's confusing. Honestly, I'm already thinking about the framer
codebase refactoring, but this is a big piece of work, and I'm unsure if we
really win a lot here. Anyway, changes to the protocol happen not that often
> 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]
