You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Russole (via GitHub)" <gi...@apache.org> on 2025/12/08 12:36:26 UTC
[PR] Hdds 8511. Allow only FSO type of bucket to be created with bucket name including non-S3 compliant charaters when the om server side config 'ozone.om.namespace.s3.strict' is set false [ozone]
Russole opened a new pull request, #9462:
URL: https://github.com/apache/ozone/pull/9462
## What changes were proposed in this pull request?
This patch limits the non-strict naming behavior only to FSO buckets, which do not rely on S3 naming semantics.
Legacy/ObjectStore buckets—which represent the S3 bucket layout in Ozone—continue to enforce strict, S3-compliant naming rules, even when strict mode is disabled.
In summary, this PR ensures that only FSO buckets may use non-strict bucket names when
ozone.om.namespace.s3.strict=false; S3 buckets (Legacy/ObjectStore) must remain strict.
## Appoach
* Updated OMBucketCreateRequest to apply non-strict bucket name validation only when strict mode is disabled and the bucket layout is FSO.
* Ensured that S3 buckets (Legacy/ObjectStore layout) always enforce strict, S3-compliant naming rules, regardless of the strict-mode setting.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8511
## How was this patch tested?
I relied on existing unit and integration tests, and verified that the full CI passed on my fork.
Please let me know if additional tests are needed.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "adoroszlai (via GitHub)" <gi...@apache.org>.
adoroszlai commented on code in PR #9462:
URL: https://github.com/apache/ozone/pull/9462#discussion_r2636875561
##########
hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/request/bucket/TestOMBucketCreateRequest.java:
##########
@@ -478,4 +478,28 @@ public static void addCreateVolumeToTable(String volumeName,
.setOwnerName(UUID.randomUUID().toString()).build();
OMRequestTestUtils.addVolumeToOM(omMetadataManager, omVolumeArgs);
}
+
+ protected OMBucketCreateRequest doPreExecute(String volumeName,
+ String bucketName,
+ OzoneManagerProtocolProtos.BucketLayoutProto layout) throws Exception {
Review Comment:
nit: Please do not format method signature like this. Whenever visibility / return type / method name / other modifiers are changed, we would have to reindent all parameters.
##########
hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/request/bucket/TestOMBucketCreateRequestWithObjectStore.java:
##########
@@ -0,0 +1,72 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.hadoop.ozone.om.request.bucket;
+
+import static org.apache.hadoop.ozone.om.request.OMRequestTestUtils.newBucketInfoBuilder;
+import static org.apache.hadoop.ozone.om.request.OMRequestTestUtils.newCreateBucketRequest;
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertThrows;
+
+import java.util.UUID;
+import org.apache.hadoop.ozone.om.OMConfigKeys;
+import org.apache.hadoop.ozone.om.exceptions.OMException;
+import org.apache.hadoop.ozone.protocol.proto.OzoneManagerProtocolProtos;
+import org.apache.hadoop.ozone.protocol.proto.OzoneManagerProtocolProtos.OMRequest;
+import org.junit.jupiter.api.BeforeEach;
+import org.junit.jupiter.api.Test;
+
+/**
+ * Tests bucket creation behavior for ObjectStore / Legacy bucket layouts.
+ */
+public class TestOMBucketCreateRequestWithObjectStore extends TestOMBucketCreateRequest {
+
+ @BeforeEach
+ public void setupWithObjectStore() {
+ ozoneManager.getConfiguration().set(
+ OMConfigKeys.OZONE_DEFAULT_BUCKET_LAYOUT,
+ OMConfigKeys.OZONE_BUCKET_LAYOUT_OBJECT_STORE);
+ }
+
+ @Test
+ public void testNonS3BucketNameRejectedForObjectStoreWhenStrictDisabled()
+ throws Exception {
+
+ // strict mode disabled
+ ozoneManager.getConfiguration().setBoolean(
+ OMConfigKeys.OZONE_OM_NAMESPACE_STRICT_S3, false);
+
+ String volumeName = UUID.randomUUID().toString();
+ String bucketName = "bucket_with_underscore"; // non-S3-compliant
+ addCreateVolumeToTable(volumeName, omMetadataManager);
+
+ // Explicitly set bucket layout to OBJECT_STORE so the test doesn't depend on
+ // defaults or mocked OM behavior.
+ OzoneManagerProtocolProtos.BucketInfo.Builder bucketInfo =
+ newBucketInfoBuilder(bucketName, volumeName)
+ .setBucketLayout(
+ OzoneManagerProtocolProtos.BucketLayoutProto.OBJECT_STORE);
Review Comment:
Then we don't need this new test class, test case can be added in `TestOMBucketCreateRequest`.
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/bucket/OMBucketCreateRequest.java:
##########
@@ -93,9 +94,17 @@ public OMRequest preExecute(OzoneManager ozoneManager) throws IOException {
CreateBucketRequest createBucketRequest =
getOmRequest().getCreateBucketRequest();
BucketInfo bucketInfo = createBucketRequest.getBucketInfo();
- // Verify resource name
- OmUtils.validateBucketName(bucketInfo.getBucketName(),
- ozoneManager.isStrictS3());
+
+ BucketLayout bucketLayout = BucketLayout.fromProto(bucketInfo.getBucketLayout());
+ OmConfig omConfig = ozoneManager.getConfig();
+ boolean fsPathEnabled = false;
+ if (omConfig != null) {
+ fsPathEnabled = omConfig.isFileSystemPathEnabled();
+ }
Review Comment:
Instead of adding this logic, please mock `ozoneManager.getConfig()` in `TestOMClientRequestWithUserInfo`:
https://github.com/apache/ozone/blob/66cb1e72606e206352f54282e7f19461ad7761bc/hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/request/TestOMClientRequestWithUserInfo.java#L80
like:
https://github.com/apache/ozone/blob/66cb1e72606e206352f54282e7f19461ad7761bc/hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/request/file/TestOMDirectoryCreateRequest.java#L101-L102
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "Russole (via GitHub)" <gi...@apache.org>.
Russole commented on PR #9462:
URL: https://github.com/apache/ozone/pull/9462#issuecomment-3684290061
I re-ran the job on my fork and it passed.
I don’t have permission to rerun the upstream CI,
so I’d appreciate it if someone could help rerun the failed job.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on code in PR #9462:
URL: https://github.com/apache/ozone/pull/9462#discussion_r2652056991
##########
hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/request/bucket/TestOMBucketCreateRequest.java:
##########
@@ -478,4 +506,25 @@ public static void addCreateVolumeToTable(String volumeName,
.setOwnerName(UUID.randomUUID().toString()).build();
OMRequestTestUtils.addVolumeToOM(omMetadataManager, omVolumeArgs);
}
+
+ protected OMBucketCreateRequest doPreExecute(String volumeName,
+ String bucketName,
+ OzoneManagerProtocolProtos.BucketLayoutProto layout) throws Exception {
+ OzoneManagerProtocolProtos.BucketInfo.Builder bucketInfo =
+ newBucketInfoBuilder(bucketName, volumeName)
+ .setBucketLayout(layout);
+ if (layout == OzoneManagerProtocolProtos.BucketLayoutProto.FILE_SYSTEM_OPTIMIZED) {
+ bucketInfo.addMetadata(OMRequestTestUtils.fsoMetadata());
+ }
+ return doPreExecute(bucketInfo);
+ }
Review Comment:
I think this extra `doPreExecute` is not necessary. How about we simply use the current `newBucketInfoBuilder#setBucketLayout(FILE_SYSTEM_OPTIMIZED)`? Also the `addMetadata` is also not necessary.
##########
hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/request/bucket/TestOMBucketCreateRequestWithFSO.java:
##########
@@ -182,4 +183,36 @@ protected void doValidateAndUpdateCache(String volumeName, String bucketName,
verifySuccessCreateBucketResponse(omClientResponse.getOMResponse());
}
+
+ @Test
+ public void testNonS3BucketNameAllowedForFSOWhenStrictDisabled() throws Exception {
+ // Arrange
+ ozoneManager.getConfiguration().setBoolean(
+ OMConfigKeys.OZONE_OM_NAMESPACE_STRICT_S3, false); // 如果常數名稱不同，改成實際的 key
Review Comment:
Nit: Please remove the mandarin comment (since some community members may not understand it) and the "Arrange" comment also can be removed.
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/bucket/OMBucketCreateRequest.java:
##########
@@ -93,9 +93,11 @@ public OMRequest preExecute(OzoneManager ozoneManager) throws IOException {
CreateBucketRequest createBucketRequest =
getOmRequest().getCreateBucketRequest();
BucketInfo bucketInfo = createBucketRequest.getBucketInfo();
- // Verify resource name
- OmUtils.validateBucketName(bucketInfo.getBucketName(),
- ozoneManager.isStrictS3());
+
+ BucketLayout bucketLayout = BucketLayout.fromProto(bucketInfo.getBucketLayout());
+ boolean strict = ozoneManager.isStrictS3()
+ || bucketLayout.isObjectStore(ozoneManager.getConfig().isFileSystemPathEnabled());
Review Comment:
Let's only check for OBS bucket (i.e. not use `BucketLayout#isObjectStore` which also takes into account LEGACY buckets) since it provides a stronger guarantee than LEGACY bucket which can become "object store" if we change the configuration ("ozone.om.enable.filesystem.paths").
Also let's add a small comment that OBS bucket needs to have strictly S3 name bucket unlikes FSO and LEGACY bucket.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "ashishkumar50 (via GitHub)" <gi...@apache.org>.
ashishkumar50 commented on code in PR #9462:
URL: https://github.com/apache/ozone/pull/9462#discussion_r2652427570
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/bucket/OMBucketCreateRequest.java:
##########
@@ -93,9 +93,11 @@ public OMRequest preExecute(OzoneManager ozoneManager) throws IOException {
CreateBucketRequest createBucketRequest =
getOmRequest().getCreateBucketRequest();
BucketInfo bucketInfo = createBucketRequest.getBucketInfo();
- // Verify resource name
- OmUtils.validateBucketName(bucketInfo.getBucketName(),
- ozoneManager.isStrictS3());
+
+ BucketLayout bucketLayout = BucketLayout.fromProto(bucketInfo.getBucketLayout());
+ boolean strict = ozoneManager.isStrictS3()
+ || bucketLayout.isObjectStore(ozoneManager.getConfig().isFileSystemPathEnabled());
Review Comment:
Yes I think let's keep this s3 strict compliant name only for OBS buckets.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "Russole (via GitHub)" <gi...@apache.org>.
Russole commented on PR #9462:
URL: https://github.com/apache/ozone/pull/9462#issuecomment-3701788548
Thanks @ivandika3 and @ashishkumar50 for the review. I've addressed the comments and updated the patch accordingly.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for OBJECT_STORE buckets [ozone]
Posted by "adoroszlai (via GitHub)" <gi...@apache.org>.
adoroszlai commented on code in PR #9462:
URL: https://github.com/apache/ozone/pull/9462#discussion_r2616794403
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/bucket/OMBucketCreateRequest.java:
##########
@@ -93,9 +94,41 @@ public OMRequest preExecute(OzoneManager ozoneManager) throws IOException {
CreateBucketRequest createBucketRequest =
getOmRequest().getCreateBucketRequest();
BucketInfo bucketInfo = createBucketRequest.getBucketInfo();
+
+ // Convert BucketLayoutProto -> BucketLayout enum.
+ BucketLayout bucketLayout =
+ BucketLayout.valueOf(bucketInfo.getBucketLayout().name());
+
+ // Determine if this bucket belongs to the S3 namespace.
+ String s3VolumeName = ozoneManager.getConfiguration().get(
+ OzoneConfigKeys.OZONE_S3_VOLUME_NAME,
+ OzoneConfigKeys.OZONE_S3_VOLUME_NAME_DEFAULT);
+ boolean isS3Bucket =
+ s3VolumeName != null && s3VolumeName.equals(bucketInfo.getVolumeName());
+
+ // Compute effectiveStrict based on global strict flag, S3 namespace,
+ // and bucket layout.
+ boolean globalStrict = ozoneManager.isStrictS3();
+ boolean effectiveStrict = globalStrict;
+
+
+ // When strict=false, only S3 buckets with FSO layout should allow
+ // non-S3-compliant characters (e.g. underscore).
+ // All other S3 bucket layouts must still enforce strict naming rules.
+ if (!globalStrict && isS3Bucket) {
+ if (bucketLayout == BucketLayout.FILE_SYSTEM_OPTIMIZED) {
+ // S3 + FSO + strict=false → bypass strict S3 validation (allow '_' and other non-S3 characters)
+ effectiveStrict = false;
+ } else {
+ // S3 + non-FSO + strict=false → strict S3 validation still applies
+ // '_' and other non-S3 characters are not permitted
+ effectiveStrict = true;
+ }
+ }
+
// Verify resource name
OmUtils.validateBucketName(bucketInfo.getBucketName(),
- ozoneManager.isStrictS3());
+ effectiveStrict);
Review Comment:
1. Considering bucket links, multitenancy, and that S3 volume name can be updated in the config, I don't think this should be restricted to buckets in the S3 volume.
2. Check eligibility using `bucketLayout#isObjectStore` to handle `LEGACY`, too.
3. Use existing conversion logic `BucketLayout#fromProto`.
```suggestion
BucketLayout bucketLayout = BucketLayout.fromProto(bucketInfo.getBucketLayout());
boolean strict = ozoneManager.isStrictS3()
|| bucketLayout.isObjectStore(ozoneManager.getConfig().isFileSystemPathEnabled());
OmUtils.validateBucketName(bucketInfo.getBucketName(), strict);
```
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "Russole (via GitHub)" <gi...@apache.org>.
Russole commented on PR #9462:
URL: https://github.com/apache/ozone/pull/9462#issuecomment-3706590708
Thanks @ivandika3, @sreejasahithi, @adoroszlai, @Tejaskriya, and @ashishkumar50 for the reviews. Thanks a lot!
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] Hdds 8511. Allow only FSO type of bucket to be created with bucket name including non-S3 compliant charaters when the om server side config 'ozone.om.namespace.s3.strict' is set false [ozone]
Posted by "sreejasahithi (via GitHub)" <gi...@apache.org>.
sreejasahithi commented on PR #9462:
URL: https://github.com/apache/ozone/pull/9462#issuecomment-3627307216
Volume based S3 bucket detection does not look completely right because what I understand is that in multi-tenancy S3 requests route to respective tenant volumes (not always s3v) as each tenant has its own designated volume. I think its better to do by bucket layout and not by volume name.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on PR #9462:
URL: https://github.com/apache/ozone/pull/9462#issuecomment-3704390731
Thanks @Russole for the patch and @adoroszlai @ashishkumar50 for the reviews.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 merged PR #9462:
URL: https://github.com/apache/ozone/pull/9462
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "Russole (via GitHub)" <gi...@apache.org>.
Russole commented on PR #9462:
URL: https://github.com/apache/ozone/pull/9462#issuecomment-3658133681
Thanks @sreejasahithi, @adoroszlai, and @Tejaskriya for the detailed reviews.
I’ll start updating the patch based on your comments.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-8511. Enforce strict S3-compliant name for object store buckets [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on code in PR #9462:
URL: https://github.com/apache/ozone/pull/9462#discussion_r2652049621
##########
hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/request/bucket/TestOMBucketCreateRequestWithFSO.java:
##########
@@ -182,4 +183,36 @@ protected void doValidateAndUpdateCache(String volumeName, String bucketName,
verifySuccessCreateBucketResponse(omClientResponse.getOMResponse());
}
+
+ @Test
+ public void testNonS3BucketNameAllowedForFSOWhenStrictDisabled() throws Exception {
+ // Arrange
+ ozoneManager.getConfiguration().setBoolean(
+ OMConfigKeys.OZONE_OM_NAMESPACE_STRICT_S3, false); // 如果常數名稱不同，改成實際的 key
Review Comment:
Nit: Please remove the zh comment (since some community members may not understand it) and the "Arrange" comment also can be removed.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org