bugs – if a major version later we force upgrade, then they have a
> whole
> >>> range of major versions to downgrade to that still support this feature
> >>> (but perhaps avoid some other new issue)
> >>>
> >>>
> >>>
> >>
portant thing to avoid is providing users no version buffer to escape new
>>> bugs – if a major version later we force upgrade, then they have a whole
>>> range of major versions to downgrade to that still support this feature
>>> (but perhaps avoid some other new issue)
&g
support this feature
> > (but perhaps avoid some other new issue)
> >
> >
> >
> > From: Jacek Lewandowski
> > Date: Tuesday, 26 October 2021 at 12:01
> > To: dev@cassandra.apache.org
> > Subject: Re: [DISCUSS] How to implement backward
ade to that still support this feature
> (but perhaps avoid some other new issue)
>
>
>
> From: Jacek Lewandowski
> Date: Tuesday, 26 October 2021 at 12:01
> To: dev@cassandra.apache.org
> Subject: Re: [DISCUSS] How to implement backward compatibility
> (CASSANDRA-1704
major versions
to downgrade to that still support this feature (but perhaps avoid some other
new issue)
From: Jacek Lewandowski
Date: Tuesday, 26 October 2021 at 12:01
To: dev@cassandra.apache.org
Subject: Re: [DISCUSS] How to implement backward compatibility (CASSANDRA-17048)
Though, the user
The user will be able to test the new feature in a testing environment
and not push the changes to their production environment if they are not
satisfied.
On 26/10/2021 12:00, Jacek Lewandowski wrote:
Though, the user is unable to test the new feature without enabling it. And
when it is enable
Though, the user is unable to test the new feature without enabling it. And
when it is enabled, the user is unable to revert it.
- - -- --- - -
Jacek Lewandowski
On Tue, Oct 26, 2021 at 12:54 PM Bowen Song wrote:
> Personally, I would prefer a transition period in whic
Personally, I would prefer a transition period in which the new feature
is not enabled by default. This not only makes version upgrading easier,
it also allows the user to stay on the old behaviour if they experience
any issue with the new feature (e.g.: bugs in the new feature, or edge
use cas
Hi,
In short, we are discussing UUID based sstable generation identifiers in
https://issues.apache.org/jira/browse/CASSANDRA-17048.
The question which somehow hold us is support for downgrading. Long story
short, when we generate new sstables with uuid based ids, they are not readable
by olde
