sodonnel opened a new pull request #3141:
URL: https://github.com/apache/ozone/pull/3141
## What changes were proposed in this pull request?
Listing they key details looks like the following:
```
$ ozone sh key info /vol1/bucket1/key5
{
"volumeName" : "vol1",
"bucketName" : "bucket1",
"name" : "key5",
"dataSize" : 174,
"creationTime" : "2022-02-27T21:38:48.816Z",
"modificationTime" : "2022-02-27T21:38:49.526Z",
"replicationConfig" : {
"replicationFactor" : "THREE",
"requiredNodes" : 3,
"replication" : "THREE",
"replicationType" : "RATIS"
},
"ozoneKeyLocations" : [ {
"containerID" : 5,
"localID" : 109611004723200006,
"length" : 174,
"offset" : 0,
"keyOffset" : 0
} ],
"metadata" : { },
"replicationType" : "RATIS",
"replicationFactor" : 3
}
```
ReplicationType and Factor are now contained in ReplicationConfig, so we
should not display them in the JSON output. Also note that the
replicationFactor is duplicated inside replicationConfig.replication since we
added [HDDS-6308](https://issues.apache.org/jira/browse/HDDS-6308), so we
should probably also JsonIgnore those new fields to prevent the duplication in
the command output.
After this change, the output looks like:
```
$ ozone sh key list /vol1/bucket1
[ {
"volumeName" : "vol1",
"bucketName" : "bucket1",
"name" : "key1",
"dataSize" : 174,
"creationTime" : "2022-02-27T23:11:47.227Z",
"modificationTime" : "2022-02-27T23:11:48.239Z",
"replicationConfig" : {
"replicationFactor" : "THREE",
"requiredNodes" : 3,
"replicationType" : "RATIS"
}
}, {
"volumeName" : "vol1",
"bucketName" : "bucket1",
"name" : "key2",
"dataSize" : 174,
"creationTime" : "2022-02-27T23:12:53.377Z",
"modificationTime" : "2022-02-27T23:12:54.308Z",
"replicationConfig" : {
"data" : 3,
"parity" : 2,
"ecChunkSize" : 1048576,
"codec" : "RS",
"replicationType" : "EC",
"requiredNodes" : 5
}
} ]
```
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6380
## How was this patch tested?
Manually via docker-compose cluster
--
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]
