bshashikant commented on pull request #1586: URL: https://github.com/apache/ozone/pull/1586#issuecomment-729622739
> Shouldn't Ratis be backward compatible now that it has reached 1.0? Dropping existing API and renaming config keys without handling old ones look incompatible to me. Maybe this is not the right place to discuss this, but the changes necessary in Ozone to upgrade Ratis highlights these issues. @adoroszlai , i agree with you. This needs better handling for upgrade cases. @avijayanhwx , any thoughts on this? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
