[
https://issues.apache.org/jira/browse/HDDS-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538074#comment-17538074
]
Attila Doroszlai commented on HDDS-6758:
----------------------------------------
[~sadanand_shenoy], bucket links should not have any layout. They are just
pointers.
> Ozone bucket Info doesn’t print bucket layout for linked buckets
> ----------------------------------------------------------------
>
> Key: HDDS-6758
> URL: https://issues.apache.org/jira/browse/HDDS-6758
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Sadanand Shenoy
> Priority: Major
>
> The ozone sh bucket info command doesn’t print info about the bucket type.
> {code:java}
> [root@repdst-1 ~]# ozone sh bucket link /vol1/buck1 /s3v/linkedbuck1
> 22/05/17 07:56:24 INFO rpc.RpcClient: Creating Bucket: s3v/linkedbuck1, with
> root as owner and Versioning false and Storage Type set to DISK and
> Encryption set to false
> [root@repdst-1 ~]# ozone sh bucket info /s3v/linkedbuck1
> {
> "volumeName" : "s3v",
> "bucketName" : "linkedbuck1",
> "sourceVolume" : "vol1",
> "sourceBucket" : "buck1",
> "creationTime" : "2022-05-17T07:56:24.059Z",
> "modificationTime" : "2022-05-17T07:56:24.059Z"
> }
> [root@repdst-1 ~]# {code}
> Now that we have bucket types , what is the default type when a linked bucket
> is created ?
> Looking at the code it looks like the client would not set the bucket layout
> in bucket args. This would mean the bucket type would be according to the
> default server defined bucket type.
> {code:java}
> BucketArgs.Builder bb = new BucketArgs.Builder()
> .setStorageType(StorageType.DEFAULT)
> .setVersioning(false)
> .setSourceVolume(source.getVolumeName())
> .setSourceBucket(source.getBucketName()); {code}
> This would make it possible to link OBS to FSO and vice-versa. Should this be
> allowed?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
