xichen01 commented on code in PR #11229:
URL: https://github.com/apache/ozone/pull/11229#discussion_r4119787903
##########
hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/util/S3Consts.java:
##########
@@ -131,6 +131,11 @@ public final class S3Consts {
/** Request header carrying the list of object attributes to return. */
public static final String OBJECT_ATTRIBUTES_HEADER =
"x-amz-object-attributes";
+ // S3 storage class values passed via the `x-amz-storage-class` request
header.
+ public static final String S3_STORAGE_CLASS_STANDARD = "STANDARD";
+ public static final String S3_STORAGE_CLASS_STANDARD_IA = "STANDARD_IA";
+ public static final String S3_STORAGE_CLASS_GLACIER = "GLACIER";
+
Review Comment:
I think we could add replication-type semantics to `S3StorageClass`.
However, we currently map `STANDARD_IA` to a fixed `EC 3-2` configuration in
`S3StorageType`, whereas EC configurations can vary.
In our internal implementation, we map `DEEP_ARCHIVE` to `EC + WARM`; the
specific EC type is determined by configuration, and the EC component for
`DEEP_ARCHIVE` is fixed to the `WARM` tier.
For reverse mapping, any combination of EC and WARM can be mapped to
DEEP_ARCHIVE; the system does not check whether the specific EC configuration
is 3+2 or 4+2.
Additionally, `3-2` is not a configuration that supports multiple zones,
whereas EC configurations like `4-2`, `6-3`, or `9-3` easily facilitate a
3-zone setup. Multi-zone EC requires at least three zones to ensure data
availability.
--
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]
