You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "satish babu krishnamoorthy (Commented) (JIRA)" <ji...@apache.org> on 2011/10/10 19:12:29 UTC
[jira] [Commented] (CASSANDRA-3326) Add timing information to
cassandra-cli queries
[ https://issues.apache.org/jira/browse/CASSANDRA-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124306#comment-13124306 ]
satish babu krishnamoorthy commented on CASSANDRA-3326:
-------------------------------------------------------
Yes, it make sense to add timing info for all the commands.
> Add timing information to cassandra-cli queries
> -----------------------------------------------
>
> Key: CASSANDRA-3326
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3326
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Affects Versions: 1.0.0
> Reporter: Radim Kolar
> Assignee: satish babu krishnamoorthy
> Priority: Minor
> Labels: cli
> Fix For: 1.0.1
>
> Attachments: 3326.patch
>
>
> It would be highly helpful for monitoring cluster health to return ETA on queries in cassandra-cli. MySQL is doing it too and you can switch this feature on in Postgresql and Oracle CLI.
> get testdb[234123];
> Returned 0 results *in 0.08 ms*.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira