Hi all, I've filed HDDS-15728 to propose S3-compatible object versioning in Ozone, and I'd like to bring it to wider attention before the design settles.
JIRA: https://issues.apache.org/jira/browse/HDDS-15728 Design doc: https://docs.google.com/document/d/1uT3Hzss5gJkiuxzzeZYVUB_UqjSbqROUApY5pH6k8TI/edit?usp=sharing Feature branch: https://github.com/apache/ozone/tree/HDDS-15728 Amazon S3 supports bucket-level object versioning, which keeps multiple versions of an object under the same key and allows recovery from accidental overwrites and deletions. The design document covers the bucket versioning states (Enabled / Suspended), version ID generation, null version semantics across state transitions, delete markers, and the changes required in OM metadata and the S3 Gateway API surface. Since this touches the OM metadata layout and the S3 API compatibility surface, feedback on the metadata design and on upgrade/compatibility implications would be especially valuable. Comments are welcome on the JIRA, in the doc, or on this thread. Thanks, Yiyang
