You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2026/07/30 22:57:00 UTC

[jira] [Created] (HDDS-16044) Do not use the unified versioning framework until ZDU is finalized

Ethan Rose created HDDS-16044:
---------------------------------

             Summary: Do not use the unified versioning framework until ZDU is finalized
                 Key: HDDS-16044
                 URL: https://issues.apache.org/jira/browse/HDDS-16044
             Project: Apache Ozone
          Issue Type: Improvement
            Reporter: Ethan Rose
            Assignee: Ethan Rose


ZDU is the first version that supports the unified versioning framework, where network and disk compatibility are tracked with the same version. Therefore, we cannot use this framework before ZDU is finalized. The existing {{VersionManager}} already handles this for disk compatibility. It will read from the old layout feature enums until ZDU is finalized. We need similar handling for the component version sent over the network to clients. We cannot send the unified version framework's apparent version to clients until ZDU is finalized, otherwise we may be sending them a layout feature when they are expecting a component version. When ZDU is pre-finalized, we must send the last component version before ZDU to clients. Finalizing ZDU moves both version systems ahead to the unified one that starts with ZDU, where one apparent version can be shared over both disk and network.

HDDS-15641 will handle this for SCM/Datanodes on the write path. This Jira will handle it for the remaining cases on the HDDS read path and OM {{getServiceInfo}} call.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org