You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Janus Chow (Jira)" <ji...@apache.org> on 2026/08/21 01:57:00 UTC
[jira] [Updated] (HDDS-16014) [Ozone versioning] [T3] Enabled Write Path
[ https://issues.apache.org/jira/browse/HDDS-16014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Janus Chow updated HDDS-16014:
------------------------------
Description:
This ticket includes the following tasks:
|*Sub-task*|*Scope*|*Acceptance*|
|T3.1 PUT commit two-table update|old current → versionedKeyTable, new current into keyTable, one WriteBatch|after overwrite both versions readable; two-table cache-consistency tests|
|T3.2 DELETE inserts marker|DELETE without versionId: current moves to versionedKeyTable, marker becomes current|GET returns KEY_NOT_FOUND; the old version survives; DELETE on a marker stacks another|
|T3.3 quota accounting|all versions (incl. marker namespace usage) count against bucket quota|over-quota versioned PUT rejected (unit test); deletions deduct correctly|
|T3.4 batch DELETE inserts markers|DeleteKeys on a versioned bucket inserts one delete marker per key and demotes the version each supersedes, reusing T3.2’s implementation rather than a second copy|Batch delete leaves the bucket in the same shape a single delete would;
A suspended batch takes the null slot;
An unversioned bucket is unchanged;
S3 DeleteObjects and DeleteObject agree|
was:
This ticket includes the following tasks:
|*Sub-task*|*Scope*|*Acceptance*|
|T3.1 PUT commit two-table update|old current → versionedKeyTable, new current into keyTable, one WriteBatch|after overwrite both versions readable; two-table cache-consistency tests|
|T3.2 DELETE inserts marker|DELETE without versionId: current moves to versionedKeyTable, marker becomes current|GET returns KEY_NOT_FOUND; the old version survives; DELETE on a marker stacks another|
|T3.3 quota accounting|all versions (incl. marker namespace usage) count against bucket quota|over-quota versioned PUT rejected (unit test); deletions deduct correctly|
> [Ozone versioning] [T3] Enabled Write Path
> ------------------------------------------
>
> Key: HDDS-16014
> URL: https://issues.apache.org/jira/browse/HDDS-16014
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Janus Chow
> Assignee: Janus Chow
> Priority: Major
> Labels: pull-request-available
>
> This ticket includes the following tasks:
> |*Sub-task*|*Scope*|*Acceptance*|
> |T3.1 PUT commit two-table update|old current → versionedKeyTable, new current into keyTable, one WriteBatch|after overwrite both versions readable; two-table cache-consistency tests|
> |T3.2 DELETE inserts marker|DELETE without versionId: current moves to versionedKeyTable, marker becomes current|GET returns KEY_NOT_FOUND; the old version survives; DELETE on a marker stacks another|
> |T3.3 quota accounting|all versions (incl. marker namespace usage) count against bucket quota|over-quota versioned PUT rejected (unit test); deletions deduct correctly|
> |T3.4 batch DELETE inserts markers|DeleteKeys on a versioned bucket inserts one delete marker per key and demotes the version each supersedes, reusing T3.2’s implementation rather than a second copy|Batch delete leaves the bucket in the same shape a single delete would;
> A suspended batch takes the null slot;
> An unversioned bucket is unchanged;
> S3 DeleteObjects and DeleteObject agree|
--
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