[
https://issues.apache.org/jira/browse/HDDS-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787368#comment-17787368
]
Stephen O'Donnell commented on HDDS-9700:
-----------------------------------------
[~erose] I have this working (PR next week hopefully), but I am fighting with
allow input via stdin in a nice way. Currently for the json if there is an
error with a container, I output:
{ "error": "The error message }
I believe that all elements in a JSON array not have to be the same type, so
this is valid JSON:
{code}
[
{
"container": {
...
}
},
{ "error": "some message" },
{
"container": {
}
}
]
{code}
> Allow ozone admin container info to list multiple containers
> ------------------------------------------------------------
>
> Key: HDDS-9700
> URL: https://issues.apache.org/jira/browse/HDDS-9700
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM Client
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
>
> Currently the command:
> {code}
> ozone admin container info 1234
> {code}
> Only accepts a single container ID. If you need to list the details from many
> containers, then the JVM startup overhead makes the command very slow.
> Therefore it would be useful to allow a list of IDs to be specified so a
> single JVM instance can retrieve all the details in a single call.
> The logic should handle invalid IDs and "unknown to SCM containers" by
> printing an error and continuing to the next ID rather than failing.
> For the JSON output, it probably makes sense to output a JSON array rather
> than a series of individual JSON blob, so the entire output can be pass to a
> JSON tool without modification.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
