Yes, that is true, but the original, unfixed, output, is still there. Are we OK
with that?
Now the command "nodetool command" writes this:
someValue: 1
Another Value: 2
The Third Value: 3
You say that, lets add a flag to this too, -j (as in json), so a user will get:
{
"some_value": 1,
"another_value": 2,
"the_third_value": 3
}
Correct?
But the original discrepancy, "someValue" instead of "Some Value", is still
there.
Is this OK for everybody?
My aim is to fix the original output too and having "-j" flag is just nice to
have, just another way how to interpret the results. But you mean that we are
not going to touch "someValue" output ever again?
________________________________________
From: Brandon Williams <[email protected]>
Sent: Friday, July 7, 2023 21:05
To: [email protected]
Subject: Re: Changing the output of tooling between majors
NetApp Security WARNING: This is an external email. Do not click links or open
attachments unless you recognize the sender and know the content is safe.
On Fri, Jul 7, 2023 at 2:02 PM Miklosovic, Stefan
<[email protected]> wrote:
>
> There is just no clear path how to improve that over time and exposing the
> same output via different format is not really solving it ... the
> discrepancies are still there.
I'm not sure what you mean, can you explain? In my mind, if we have a
serialized output format, we have divorced the display from the data
and so we should be free to modify how we display it all we like after
that point.
