ArafatKhan2198 commented on PR #4182: URL: https://github.com/apache/ozone/pull/4182#issuecomment-1485850945
Therefore, to conclude, there is no need for any conversion from `object-ID` to vol/bucket Name. Our goal should be to ensure that both the FSO and OBS keys are stored in the ContainerKey table, as it serves as the source of information for this endpoint. For Example :- <pre><code class="language-bash">ozone sh bucket create --layout FILE_SYSTEM_OPTIMIZED /s3v/fso-bucket ozone sh key put s3v/fso-bucket/key1-fso NOTICE.txt ozone sh key put s3v/fso-bucket/key2-fso NOTICE.txt ozone sh bucket create --layout OBJECT_STORE /s3v/obs-bucket ozone sh key put s3v/obs-bucket/key1-obs NOTICE.txt ozone sh key put s3v/obs-bucket/key2-obs NOTICE.txt ozone sh bucket create --layout LEGACY s3v/legacy-bucket ozone sh key put s3v/legacy-bucket/key1-legacy NOTICE.txt ozone sh key put s3v/legacy-bucket/key2-legacy NOTICE.txt </code></pre> The ContainerKey Table generated for this data would be the below table :- In which the FSO key information would be displayed in the form of Object-ID's KeyPrefix | Container ID -- | -- /-4611686018427388160/-9223372036854774528/-9223372036854774528/key1-fso | 1 /s3v/obs-bucket/key2-obs | 1 /-4611686018427388160/-9223372036854774528/-9223372036854774528/key2-fso | 2 /s3v/legacy-bucket/key1-legacy | 2 /s3v/legacy-bucket/key2-legacy | 3 /s3v/obs-bucket/key1-obs | 3 -- 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]
