hevinhsu commented on code in PR #8558:
URL: https://github.com/apache/ozone/pull/8558#discussion_r2141528170
##########
hadoop-ozone/integration-test-s3/src/test/java/org/apache/hadoop/ozone/s3/awssdk/v2/AbstractS3SDKV2Tests.java:
##########
@@ -621,4 +648,512 @@ private void completeMultipartUpload(String bucketName,
String key, String uploa
assertEquals(bucketName, compResponse.bucket());
assertEquals(key, compResponse.key());
}
+
+ @Nested
+ @TestInstance(TestInstance.Lifecycle.PER_CLASS)
+ class S3BucketVerificationConditionTests {
+
+ private static final String DEFAULT_BUCKET_NAME = "default-bucket";
+ private String correctOwner;
+ private static final String WRONG_OWNER = "wrong-owner";
+ private static final String BUCKET_VERIFICATION_TEST_KEY = "test-key";
+
+ @BeforeAll
+ public void setup() throws Exception {
Review Comment:
Hi @ivandika3
I tested the dangling bucket scenario. After deleting the source bucket, I
noticed that the linked bucket under ```/s3v``` still retains the owner field.
Here are the commands I used, executed via Docker Compose under
```ozone/hadoop-ozone/dist/target/ozone-2.1.0-SNAPSHOT/compose/ozone```:
```sh
ozone sh volume create /test
ozone sh volume create /s3v
ozone sh bucket create /test/source
ozone sh bucket link /test/source /s3v/link
ozone sh bucket delete /test/source
# owner still exists
ozone sh bucket info /s3v/link
aws s3api get-bucket-acl --bucket link --endpoint-url http://s3g:9878
```
Is this the expected behavior?
--
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]
