[
https://issues.apache.org/jira/browse/HDDS-15188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18087184#comment-18087184
]
Hui Fei commented on HDDS-15188:
--------------------------------
<<Bulk update>>
Apache Ozone 2.2.0 release is in progress. I'm updating all unresolved jiras
targeting 2.2.0 to retarget 2.3.0.
> Point-In-Time View
> ------------------
>
> Key: HDDS-15188
> URL: https://issues.apache.org/jira/browse/HDDS-15188
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: OM
> Reporter: Chu Cheng Li
> Assignee: Chu Cheng Li
> Priority: Major
>
> Support to create ozone snapshot-like point in time view on existing bucket,
> then following operations like delete or update for the keys that are created
> before the PIT View, we would store the preimage of those deleted/updated
> keys, so the lookup to PIT View stay consistent.
>
> A PIT View records an OM transaction/update ID at creation time. Later
> updates/deletes under the protected bucket or prefix must preserve enough
> metadata and block references so reads through the PIT View resolve the
> newest version with updateID <= cutUpdateId.
> This likely requires:
> * a PIT View metadata table
> * shared historical version records, not one copy per PIT View
> * explicit tombstones or version end timestamps for deletes
> * a protection index so normal writes do not scan all PIT Views
> * integration with deleted key/block cleanup so visible old blocks are not
> physically reclaimed
>
> Then we could build the bucket fork feature on top of this. fork = PIT View +
> Fork Overlay.
> I am thinking if this could replace the ozone snapshot feature if we figure
> how to efficiently comparing the diff between two PIT View, the bucket
> replication/event notification might also be able to build on top of PIT View.
>
> cc [~ivandika]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
