errose28 commented on code in PR #6385:
URL: https://github.com/apache/ozone/pull/6385#discussion_r1534849499
##########
hadoop-ozone/client/src/main/java/org/apache/hadoop/ozone/client/OzoneBucket.java:
##########
@@ -469,6 +469,25 @@ public OzoneOutputStream createKey(String key, long size,
.createKey(volumeName, name, key, size, replicationConfig,
keyMetadata);
}
+ /**
+ * Overwrite an existing key using optimistic locking. The existingKey must
exist in Ozone to allow
+ * the new key to be created with the same name. Additionally, the
existingKey must not have been
+ * modified since the time its details were read. This is controlled by the
objectID and updateID
+ * fields in the existingKey. If the key is replaced the objectID will
change. If it has been updated
+ * (eg appended) the updateID will change. If either of these have changed
since the existingKey
+ * was read, either the initial key create will fail, or the key will fail
to commit after the data
+ * has been written.
Review Comment:
> This change only added the feature for Object Store buckets for now.
Ah looks like FSO is out of scope according to the PR description. We should
call that out in the API documentation as well.
--
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]
