+1. I use the smiley to let you know I'm mostly just giving you shit. ;)
On Wed, Oct 24, 2018 at 11:43 AM Benedict Elliott Smith
wrote:
> If you undertake sufficiently many low risk things, some will bite you, I
> think everyone understands that. It’s still valuable to factor a risk
> assessmen
> Now I will reinstall the old version and do the upgrade again and
> hopefully I can have more information soon.
>
Hi Tommy,
Thanks for taking the time to brave an upgrade test this early on - it
is super helpful to get this feedback.
Anyone else that has bandwidth, we very much appreciate these
If you undertake sufficiently many low risk things, some will bite you, I think
everyone understands that. It’s still valuable to factor a risk assessment
into the equation, I think?
Either way, somebody asked who didn’t have the context to easily answer, so I
did my best to offer them that in
| The risk from such a patch is very low
If I had a nickel for every time I've heard that... ;)
I'm neutral on the default change, -.5 (i.e. don't agree with it but won't
die on that hill) on the data structure change post-freeze. We put this in,
and that's a slippery slope as I'm sure we can find
Hi Jason,
Thanks for responding.
I have created two jiras for these things: CASSANDRA-14841 and
CASSANDRA-14842.
I understand the initial 4.0->3.x connection problem, since the incoming
connection from the old node isn't accepted the 4.0 node will never know
that it tries to connect to a old
