Re: V5 as a protocol beta version in 3.11

2017-11-07 Thread Alex P
This makes sense and is alongside with the previous discussions about v5. I agree with Adam and Jeremiah on that. Thank you for the input. I will adjust the tests tomorrow. Best regards, Alex Petrov > On 7. Nov 2017, at 18:32, Adam Holmberg wrote: > > I agree that it is okay to leave v5 beta

Re: V5 as a protocol beta version in 3.11

2017-11-07 Thread Adam Holmberg
I agree that it is okay to leave v5 beta behind. As I recall, the point of beta was less about trying stuff early, but more to allow early implementation and testing of new protocol features, before the scope was finalized. Now that v5 proper has diverged from beta it is no longer supported. I don'

Re: V5 as a protocol beta version in 3.11

2017-11-07 Thread J. D. Jordan
Again. V5 beta in 3.11 was always meant to stop working when future things happened to V5 in the drivers and in C*. I see no problem with leaving the beta V5, which is an opt in thing to try out, in 3.11 alone. 4.0 will have the full non beta V5 with extra stuff in it, and will not work with be

Re: V5 as a protocol beta version in 3.11

2017-11-07 Thread Oleksandr Petrov
This is an option, you're right. In this case v5 will have just one feature, however, and the only feature (Duration type) should work with via CustomTypes through v4. Looks like the Jira numbers were off, so let me do it again: In 3.11 we have: * CASSANDRA-12838 - Extend native protocol flags

Re: V5 as a protocol beta version in 3.11

2017-11-07 Thread Jonathan Haddad
The other option, to avoid having two different v5 implementations, is to bump 4.0’s protocol version to 6. On Tue, Nov 7, 2017 at 6:48 AM Jeremiah D Jordan wrote: > My 2 cents. When we added V5 to 3.x wasn’t it added as a beta protocol > for tick/tock stuff and known that when a new version cam

Re: V5 as a protocol beta version in 3.11

2017-11-07 Thread Jeremiah D Jordan
My 2 cents. When we added V5 to 3.x wasn’t it added as a beta protocol for tick/tock stuff and known that when a new version came out it would most possibly break the older releases V5 beta stuff? Or at the very least add new things to V5. So I see no reason to need to add more new features to

V5 as a protocol beta version in 3.11

2017-11-07 Thread Oleksandr Petrov
Hi everyone, Currently, 3.11 supports V5 as a protocol version. However, all new features are now going to 4.0, which is going to be a new feature release. Right now we have two v5 features: - CASSANDRA-10786 - CASSANDRA-12838