cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kurt Greaves <>
Subject Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)
Date Fri, 18 Nov 2016 21:57:05 GMT
On 18 November 2016 at 18:25, Jason Brown <> wrote:

> #11559 (enhanced node representation) - decided it's *not* something we
> need wrt #7544 storage port configurable per node, so we are punting on

#12344 - Forward writes to replacement node with same address during replace
depends on #11559. To be honest I'd say #12344 is pretty important,
otherwise it makes it difficult to replace nodes without potentially
requiring client code/configuration changes. It would be nice to get #12344
in for 4.0. It's marked as an improvement but I'd consider it a bug and
thus think it could be included in a later minor release.

Introducing all of these in a single release seems pretty risky. I think it
> would be safer to spread these out over a few 4.x releases (as they’re
> finished) and give them time to stabilize before including them in an LTS
> release. The downside would be having to maintain backwards compatibility
> across the 4.x versions, but that seems preferable to delaying the release
> of 4.0 to include these, and having another big bang release.

I don't think anyone expects 4.0.0 to be stable. It's a major version
change with lots of new features; in the production world people don't
normally move to a new major version until it has been out for quite some
time and several minor releases have passed. Really, most people are only
migrating to 3.0.x now. While stability is important if we push back large
"core" changes until later we're just setting ourselves up to face the same
issues later on. There should be enough uptake on the early releases of 4.0
from new users to help test and get it to a production-ready state.

Kurt Greaves

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message