mukul1987 edited a comment on pull request #924: URL: https://github.com/apache/hadoop-ozone/pull/924#issuecomment-630301738
> Do we need to check the backward compatibility for RPC or just for the persisted data? If only for the persisted data, it would be more useful to separated the two RPC set. backward compatibility should be on both the protos both for express as well as rolling upgrades. > What is the suggested way to use this? I assume that we can do any incompatible change with upgrading the lock file together with the proto. this fails the compilation with an error so that the user can look into the error and identify that the change is backward incompatible. > What should we put to the lock file? Is the lock file from the last release should be added and upgrade with each release? Or the first/(last?) version from the previous major line? The lock file should be committed along with the source code to identify backward incompatibility issues. ---------------------------------------------------------------- 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]
