HDDS-6838. [FSO] Sets OM default to LEGACY for an older client's bucket create request #3487
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mukul1987
reviewed
Jun 7, 2022
...e-manager/src/main/java/org/apache/hadoop/ozone/om/request/bucket/OMBucketCreateRequest.java
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Presently, older clients can create bucket other than LEGACY bucket layout if admin sets ozone.default.bucket.layout default value to FSO or OBS.
For example, ozone.default.bucket.layout = FILE_SYSTEM_OPTIMIZED in OM server.
Say, Older Client creates a bucket, OM will use the default value and creates an FSO bucket.
Now, older client can't perform any key operations to this bucket as older client's operations not supported on FSO/OBS buckets layout types.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6838
How was this patch tested?
Added test case