[ 
https://issues.apache.org/jira/browse/HDDS-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706927#comment-17706927
 ] 

Stephen O'Donnell commented on HDDS-6826:
-----------------------------------------

Copying a comment by [~umamahesh]:

{quote}
EC options are part of replicationConfig only. We never logged replication 
details there.

Irrespective of EC, we can add the info in log. It is client side info, it 
seems redundant to me as you already pass the same info above and the same 
details will be logged in INFO log. Not sure it's worth doing it so.

When we don;t specify any replication, we don't use any defaults at client 
side, instead we use at server side. createBucket API will not return anything 
back. so, we will not get any details there. So, I feel it's not really adding 
much value including replication details in info log here.
{quote}

> Need EC information included in console output while creating EC bucket
> -----------------------------------------------------------------------
>
>                 Key: HDDS-6826
>                 URL: https://issues.apache.org/jira/browse/HDDS-6826
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone CLI
>            Reporter: Nilotpal Nandi
>            Priority: Minor
>              Labels: log
>
> Need EC information included in console output while creating EC bucket
> {noformat}
> ozone sh bucket create o3://ozone1/s3v/qe-dataconn-bucket1 --type=EC 
> --replication=rs-3-2-1511k
> 22/06/02 18:24:17 INFO rpc.RpcClient: Creating Bucket: 
> s3v/qe-dataconn-bucket1, with hdfs as owner and Versioning false and Storage 
> Type set to DISK and Encryption set to false{noformat}
> Here , owner , Versioning, storage Type and encryption related information 
> present in console output.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to