errose28 opened a new pull request, #10500: URL: https://github.com/apache/ozone/pull/10500
**DRAFT** Builds on #10443 ## What changes were proposed in this pull request? The standard in the upgrade framework is that INITIAL_VERSION serializes to 0 and represents the state before any upgrade framework was introduced, meaning no version is found on disk. -1 is the in-memory serialized value representing an unknown/future version in the ComponentVersion framework. * Recon was using -1 as the in-memory placeholder to represent no version on disk, and then INITIAL_VERSION = 0 as the first version to introduce the upgrade framework. The creates a conflict with the standard versioning framework * Recon had an upgrade action tied to INITIAL_VERSION, which ran because initialization moved from version -1 to 0. After #10443 switches Recon to the new versioning framework, Recon's initialization code now reads no version being present as the initial 0 version. The upgrade action tied to version 0 will not run. To fix this, we can merge version 0's upgrade action into version 1's upgrade action, so it will still run if upgrading to this version from an old version before the versioning framework. Note that the actions will be idempotent after #10442. ## What is the link to the Apache JIRA HDDS-15349 ## How was this patch tested? Existing tests for the two upgrade actions were combined, just like the actions themselves. -- 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]
