(dropping user)

It's probably also worth mentioning that CASSANDRA-15937 will impact
what gets received on some of the JMX endpoints related to including
storage ports along with addresses, but all of the changes I view as
bugfixes on the original rather than any new functionality (for
example LoadMap / LoadMap with port outputs should be swapped and
ownership/scores are inconsistently formatted).

I expect to have a patch posted for it today, but please get in touch
if anybody has concerns about the changes.


On Fri, Jul 24, 2020 at 8:56 AM Mick Semb Wever <m...@apache.org> wrote:
>
> > This version is a beta release[1] on the 4.0 series. As always, please
> > pay attention to the release notes[2] and let us know[3] if you were
> > to encounter any problem.
>
>
>
> A quick followup note to both user and dev groups.
>
> Our Beta release guidelines¹ states that there will be no further API
> changes leading up to 4.0 GA.
> But we do currently have in place three planned exceptions to this, found in
> the following tickets:
>
> - CASSANDRA-15299 –  "CASSANDRA-13304 follow-up: improve checksumming and
> compression in protocol v5-beta"
> - CASSANDRA-15234 – Standardise config and JVM parameters
> - CASSANDRA-13701 – Lower default num_tokens
>
>
> The API changes to these are minimal, and part of the reason these were
> allowed to slip into the beta phase.
> For example…
> * CASSANDRA-15299 only affects those that are using the not yet stabilised
> v5 native protocol.
> * CASSANDRA-15234 will introduce cleaner, easier to use, cassandra.yaml
> settings, but all existing yaml setting names will still work.
> * CASSANDRA-13701 will change the default num_tokens setting to 16 (from
> 256), a change that will only impact provisioning of new clusters (because
> existing clusters must configure any new nodes to use the existing
> num_tokens value).
>
> All three tickets have fixVersion still set to `4.0-alpha` because of this
> situation.
>
>
> References:
>  [1] https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Reply via email to