errose28 opened a new pull request, #10099:
URL: https://github.com/apache/ozone/pull/10099

   **Draft since this contains and builds off of #10098**
   
   ## What changes were proposed in this pull request?
   
   This completely migrates OM to the new versioning framework. This includes:
   - Using `OMVersionManager` instead of `OMLayoutVersionManager` in all places.
     - When this was applied to `OMLayoutFeatureAspect`, it exposed a bug where 
some existing snapshot requests had not applied the annotation to `preExecute` 
and were checking against a default (always finalized) 
`OMLayoutVersionManager`. This buggy fallback path has been removed and the 
annotations moved to their correct spot.
   - `OzoneManagerVersion` instead of `OMLayoutFeature` for all new versions
   - Finalization flow and upgrade actions controlled by `OMVersionManager` 
instead of `BasicUpgradeFinalizer`/`OMUpgradeFinalizer` and 
`DefaultUpgradeFinalizationExecutor`
   - Make OM's software version `ZDU`
   
   Unused classes that were specific to OM are removed, but some classes like 
`BasicUpgradeFinalizer` are still used by HDDS Components which have not been 
migrated yet.
   
   Note that upgrade actions can still only be bound to `LayoutFeature`s. 
Because an annotation's field cannot be an interface like `ComponentVersion`, 
we cannot use the same annotation to bind upgrade actions to layout features 
and component versions. This does not cause any immediate problems since only 
existing versions tracked as `LayoutFeature`s have upgrade actions, but will 
need to be addressed in a follow-up so we can continue to add new upgrade 
actions.
   
   ## What is the link to the Apache JIRA
   
   HDDS-15063
   
   ## How was this patch tested?
   
   New functionality within the version framework was unit tested in #10098. In 
this PR all existing upgrade tests are expected to pass without regression.
   


-- 
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]

Reply via email to