Our monthly roundup of key activities and knowledge to keep the community informed.
The latest release of Apache Cassandra is 4.0.1 (pgp, sha256, and sha512). This is a rapid release to fix a critical bug in Gossip on large clusters. Please read the release notes and let us know if you encounter any problems.
Note: As the docs are not yet updated, the bintray location for Debian users is replaced with the ASF’s JFrog Artifactory location.
See the download section for the latest stable and older supported versions of source and binary distributions.
To stay up-to-date, we recommend joining the Cassandra mailing list.
Updates on Cassandra Enhancement Proposals (CEPs), how to contribute, and other community activities.
Are you new to the project? We have established a New Release tracking Kanboard and a Starter Tickets quick label that corresponds to our Low Hanging Fruit status. Any of these tickets should be of appropriate complexity for someone new to the project to tackle.
Read PMC member Josh McKenzie’s bi-weekly update for ongoing discussions and the latest on ticket progress.
The Project Management Committee (PMC) is pleased to announce that Aleksei Zotov has been invited to become a committer, and he has accepted! Thank you for all your contributions over the years, Aleksei, and congratulations! 👏
After the release of Apache Cassandra 4.0, we have many proposed features (Cassandra Enhancement Proposals or CEPs) under discussion, such as CEP-15: General Purpose Transactions and CEP-17: Storage Attached Index. The current list of CEPs and the process for proposing one are here. If you’re a developer, join the conversation today and help shape the future of Apache Cassandra!
As always, there are lots of discussions going on. Ekaterina Dimitrova started a good conversation on standardizing configuration and JVM parameters and drove a discussion on JDK 17 support, which is now being developed. We are also defining which code changes target which types of release, deciding when a minor becomes a major, for example, and when feature flags should be used. Josh McKenzie is putting together a wiki on this, and we will run a blog piece on the outcomes from the discussion in the hope it helps other open source projects facing similar questions.
The Kubernetes SIG has decided to move away from bi-weekly meetings as the original reasons for running them have been met. The SIG will be moving to a meetup-style gathering where users will share information and exchange ideas. If you want to share something at the next gathering, please contact Patrick McFadin on the cassandra-kubernetes Slack channel.
“We have modeled customer rewards data in Capital One using Apache Cassandra to serve real-time microservice-based workloads (customers accessing their rewards online) and batch Apache Spark workloads (customer statements) at the same time.” - Gokul Prabagaren
“At Glassdoor, we use Cassandra to store various datasets needed by search, machine learning models, and other systems. Since most of these systems are built on Java, we use Java drivers for Cassandra, for read, write and delete operations.” - Ravi Varsha
Do you have a Cassandra case study to share? Email email@example.com.
Datanami: Who’s Winning in Open Source Data Tech?
InfoWorld: The Long
Cassandra Powered Workflows To Automate At Scale - Maciej Swiderski
Change Data Capture for Distributed Databases @Netflix - Raghuram Onti Srinivasan
Where Apache Cassandra Fits in Your Data Platform - Mick Semb Wever
Apache Cassandra Lunch #62: Grafana Dashboard for Apache Cassandra - Sarma Pydipally