Agree. We should have some deprecation mechanism. Sorry for the inconvenience!
Tsz-Wo On Wed, Nov 25, 2020 at 1:45 AM Hanisha Koneru <[email protected]> wrote: > Hi Nicholas, > > I agree that the improvements are required and should be fixed. > > One option would be to add some deprecation mechanism for these configs. > But if there are incompatible changes which cannot be handled using > deprecation, then yes, we could make the next release 2.0. > > Thanks > Hanisha > > > On Nov 20, 2020, at 4:24 PM, Tsz Wo Sze <[email protected]> wrote: > > > > Hi Hanisha, > > > > I understand your concern on the compatibility problem and, yes, there > are > > quite a few incompatible changes in Ratis after 1.0.0 GA. Unfortunately, > > Ratis does not yet have a well-defined compatibility story. Also, there > > are a lot of rooms for improvement on the Ratis APIs. For example, typos > > like "rpcslowness.timeout -> rpc.slowness.timeout" should be fixed. > > Otherwise, it is inconsistent with the other confs. > > > > The best solution seems to make the next release 2.0.0. Similar to > Hadoop, > > our compatibility story may allow incompatibility changes between major > > releases. > > > > What do you think? > > > > Thanks a lot for starting this discussion. > > Tsz-Wo > >
