...
Zoom information: Apache Cassandra Contributor Meeting
Video Link:
Widget Connector | ||
---|---|---|
|
Agenda: Post agenda items below
- 4.0 Status
- Drivers: Addressing support for 4.0
- Thrift issues in 3.x
Meeting notes
4.0 Status
- Last alpha ticket has been assigned!
- Area that needs love - Epic tickets on testing plan
- Prioritize what needs to be tested
- Docs are now to-do free!
- Last PR was merged
- Series of blog posts for 4.0 on the way. With numbers.
- Mythbusting some of the old axioms
- Netflix has some interesting numbers around messaging
- Spread sheet for blog post topics
Drivers
- Driver support for 4.0 will be ready when 4.0 ships
- Drivers have been updated for TR meta data
- Protocol checksumming is still pending
- Java driver - 3.x version of driver and 4.x Cassandra. Request to backport 4.x changes to 3.x drivers
- Could be a problem in the community if forced to update to Java Driver 4
- Should drivers be in tree?
- Different repo for every single driver and is done intelligently with a build
- Forking drivers into ASF is a no-go based on policy of not accepting hostile forks
- What is expected from the drivers at alpha, beta and RC? Does this get in the way of testing?
- At a minimum, if somebody upgrades to c* 4.0, the driver should not break.
- <blink>Current driver 4.0 requires refactoring client code as it's API breaking</blink>
- Drivers should not get in the way of 4.0 adoption
- 2 options:
- backport 4.0 support to 3.X drivers
- Shim on the 4.0 API to be compat w/the 3.X drivers
- What driver readiness is needed per release? Let’s get this in written form.
- Release Doc: https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle
Thrift in 3.x
Netflix upgrading 2.x to 3.x and there was corruption. Trying to get a RCA