devmadhuu commented on PR #7520: URL: https://github.com/apache/ozone/pull/7520#issuecomment-2514158810
> @devabhishekpal thanks for working on the patch, however this will not solve a scenario when a user is on some version say version 1 and once user tries to upgrade our new code containing version framework say version 2, then even though user already has ozone recon and previous tables, ideally even then though our recon upgrade framework is new, all upgrade actions must be run. So we have to handle 2 scenarios: 1. Fresh cluster install where Recon is installed fresh. 2. Upgrade to new cluster version, but framework is getting introduced first in the upgraded version. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
