bharatviswa504 commented on pull request #1083: URL: https://github.com/apache/hadoop-ozone/pull/1083#issuecomment-648409228
My point here is just deleting a column family and assuming everything works with any incompatible change is wrong. >This is what we have now. If this were the only concern, we can solve it by removing this ldb subcommand when upgrade >is implemented. Today we have incompatibilities where I can accept that we need tool to help admins. Yes, for now with an incompatible change this tool may help. But using this tool to solve such issues will not solve the problem completely, let's take an example of S3 incompatible change, we need other changes like HDDS-3563. So, I am not sure just by exposing such tool, and when we see a column family is dropped and thinking that dropping a column family will resolve my upgrade issue. So, I am not sure just using this tool will help how much here. I have explained the same in one of my above comment in detail regarding this issue. https://github.com/apache/hadoop-ozone/pull/1083#issuecomment-646220673 ---------------------------------------------------------------- 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]
