5 Cassandra Enhancement Proposals Operators Should Be Watching
Anyone who’s run Cassandra at real scale has a repair story, and inevitably it starts somewhere around 2am. The good news is that a chunk of the work moving through the Cassandra Enhancement Proposal process right now is aimed at stories like that. What jumps out to me is where the effort is going, into the operational corners of Cassandra that its power users know intimately.
A CEP is how meaningful change to the open source database gets designed and argued into shape out in the open, with someone signing up to do the work and win community agreement along the way. Several have been accepted lately, and five in particular stuck out to me because, between them, they cover performance consistency, data placement, day-to-day admin, and how well Cassandra utilizes the hardware you’re paying for.
The CEPs are at varying completion stages: CEP-49 is already merged into trunk and...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
