[
https://issues.apache.org/jira/browse/CASSANDRA-14973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-14973:
----------------------------------------
Test and Documentation Plan: dtests updated to exercise new non-beta version
Status: Patch Available (was: In Progress)
I've pushed some branches/opened some PRs:
||C*||dtests||java driver||python driver||
|[14973-trunk|https://github.com/beobal/cassandra/commits/14973-trunk]|[14973|https://github.com/beobal/cassandra-dtest/tree/14973]|[PR
1529|https://github.com/datastax/java-driver/pull/1529]|[PR
1098|https://github.com/datastax/python-driver/pull/1098]|
Cirlce CI running against all the dev branches: [CircleCI |
https://app.circleci.com/pipelines/github/beobal/cassandra?branch=14973-trunk]
(ci-cassandra to follow).
Regarding the C* branch, the first 2 commits
([f373e8b|https://github.com/beobal/cassandra/commit/f373e8b720ba9667746a08ff5951cbd63c615716],
[2acc380|https://github.com/beobal/cassandra/commit/2acc380096675f5531758960356f2674ad133ed8])
replace the bundled java & python drivers with dev snapshots including
JAVA-2705 & PYTHON-1232.
The next 4 commits
([4b4788f|https://github.com/beobal/cassandra/commit/4b4788f515b6c31d74f6147a2172854ac1e1e76b],
[110ba41|https://github.com/beobal/cassandra/commit/110ba4157887e0853b79109007cccdf35db9b942],
[0aae5b4|
https://github.com/beobal/cassandra/commit/0aae5b4921a3ce6c21a8a0e977624c877b19cd5b],
[9f38772|https://github.com/beobal/cassandra/commit/9f387727692235f41a6efc0cd96a533c9109f4fa])
contain the main C* changes, including one bugfix to multi-frame messages that
running the dtests against v5 exposed.
The penultimate commit
([a3e60ee|https://github.com/beobal/cassandra/commit/a3e60eed523529b4461888b2059c428714e5ff5a]),
contains the temporary changes to have CI run against the corresponding dtest
branch, using docker images built with a compatible version of the python
driver. This commit and the two bundling the driver snapshots won't be
committed here. The proposal is that if we can get PYTHON-1232 and JAVA-2705
committed to their respective trunks, we can immediately build bundles which
reference the SHA1s and drop them in here. We should then be good to commit
this following review & a final clean CI run. We can follow up with
CASSANDRA-13951 to replace those in-tree driver binaries with release artifacts
whenever the drivers next cut those releases.
The dtest changes can be merged at any time, but will cause failures until the
python driver's {{cassandra-test}} branch includes PYTHON-1232 and the main C*
patch is landed.
> Bring v5 driver out of beta, introduce v6 before 4.0 release is cut
> -------------------------------------------------------------------
>
> Key: CASSANDRA-14973
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14973
> Project: Cassandra
> Issue Type: Task
> Reporter: Alex Petrov
> Assignee: Sam Tunnicliffe
> Priority: Urgent
> Labels: protocolv5
> Fix For: 4.0-beta
>
>
> In http://issues.apache.org/jira/browse/CASSANDRA-12142, we’ve introduced
> Beta flag for v5 protocol. However, up till now, v5 is in beta both in
> [Cassandra|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/transport/ProtocolVersion.java#L46]
> and in
> [java-driver|https://github.com/datastax/java-driver/blob/3.x/driver-core/src/main/java/com/datastax/driver/core/ProtocolVersion.java#L35].
>
> Before the final 4.0 release is cut, we need to bring v5 out of beta and
> finalise native protocol spec, and start bringing all new changes to v6
> protocol, which will be in beta.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]