Feature requests: createBucket with EC replication type for s3 clients and the precedence order changes #6773
Replies: 2 comments
-
@Lucas12138 The above code snippet ensures that in the absence of "x-amz-storage-class" header the replication type is always RATIS and From what I can see, there are multiple things to be done here.
BucketEndpoint ObjectEndpoint I created an a Epic to track all the required changes. HDDS-10980 |
Beta Was this translation helpful? Give feedback.
-
createBucket with EC replication type for s3 clients
When creating a bucket with s3 client, we cannot specify the replication type (while the ozone client supports this).
Can we add the support for the s3 client for this as well? Potentially, the input can be in the request headers.
the precedence order changes
Currently, we found the precedence order (scenarios of the actual replication type used as follows:)
1> when there's no cluster level default replication setting and no client level storage class, the replication config will be null
2> with cluster level default replication setting as EC and no client level storage class, the replication config will be Ratis
3> with cluster level default replication setting as Ratis and no client level storage class, the replication config will be Ratis
The scenario 1 and 3 makes senses but for 2, we think it should fall back to the cluster level replication setting EC.
It looks like it can be achieved by simply removing these lines:
ozone/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/endpoint/ObjectEndpoint.java
Lines 805 to 808 in f3a0dbd
Can you help verify if it's the case? Thank you
Beta Was this translation helpful? Give feedback.
All reactions