cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5977) Structure for cfstats output (JSON, YAML, or XML)
Date Fri, 18 Mar 2016 00:56:33 GMT


Yuki Morishita commented on CASSANDRA-5977:


Sorry for delay, can you re-submit the patch with the following change on the latest trunk?

- You can use generics for Maps. For exampl {{myKeyspaces}} can be ({{Map<String, Map<String,
Object>>}}). You can even create object class to hold, say, all stats for the table.
- Consider creating interface for printing. This way we can reuse those for other nodetool

> Structure for cfstats output (JSON, YAML, or XML)
> -------------------------------------------------
>                 Key: CASSANDRA-5977
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Alyssa Kwan
>            Assignee: Shogo Hoshii
>            Priority: Minor
>              Labels: Tools
>             Fix For: 3.x
>         Attachments: tablestats_sample_result.json, tablestats_sample_result.txt, tablestats_sample_result.yaml,
trunk-tablestats.patch, trunk-tablestats.patch
> nodetool cfstats should take a --format arg that structures the output in JSON, YAML,
or XML.  This would be useful for piping into another script that can easily parse this and
act on it.  It would also help those of us who use things like MCollective gather aggregate
stats across clusters/nodes.
> Thoughts?  I can submit a patch.

This message was sent by Atlassian JIRA

View raw message