CASSANDRA-15299 has revised the wire format of CQL native protocol to add a
framing layer around the existing CQL messages. This is targetted at protocol
v5, which is (still) currently in beta. There's a small problem with this
though; while v5-beta is supported in Cassandra 3.11.x and 4.0.0,
Hi Adam,
Thanks for your reply.
It's indeed a pytest version issue. Resolved by using virtualenv as
mentioned in the doc :)
cheers
Le lun. 7 déc. 2020 à 21:44, Adam Holmberg a
écrit :
> Hello. It looks like your environment might be using a newer version of
> pytest than is supported by these
Ye, that would be the alternative. We could finalise v5 as it was prior to the
new framing format, then create v6-beta in trunk only with the 15299 changes.
> On 8 Dec 2020, at 11:33, Benedict Elliott Smith wrote:
>
> Perhaps we should skip v5, and move to v6 for the new protocol to avoid this
Perhaps we should skip v5, and move to v6 for the new protocol to avoid this
issue?
On 08/12/2020, 10:53, "Sam Tunnicliffe" wrote:
CASSANDRA-15299 has revised the wire format of CQL native protocol to add a
framing layer around the existing CQL messages. This is targetted at protocol
Hey folks. I appreciate the pulse these emails lend to this release, but at
times they can be a bit sobering. While things continue to be pointed in
the right direction, you can see it’s been a bit of a slog and it got me
wondering “when might 4.0 be done?”. I did a little Jira digging to use
> …move to v6 for the new protocol to avoid this issue
+1, feels more the "grown-up thing to do".
> > Perhaps we should skip v5…
> We could finalise v5 as it was prior to the new framing format, then
create v6-beta in trunk only with the 15299 changes.
Would v5 come out of beta then in
+1 to moving v5-beta changes in trunk to new protocol v6.
Regarding 3.11 and v5, I suppose we could say, v5 could never get matured
beyond beta, but not sure if it would be confusing to see v6 while v5 is
still in beta (curious on others' thoughts as well)
On Tue, Dec 8, 2020 at 12:33 PM Mick
