cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brosius (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5823) nodetool history logging
Date Tue, 30 Jul 2013 00:25:48 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723189#comment-13723189
] 

Dave Brosius commented on CASSANDRA-5823:
-----------------------------------------

Patch seems fine generally..

It seems we are starting to litter user's home directory with files. I'd be up for renaming
the existing .cassandra-cli directory to .cassandra, and placing everything in that dir instead.

It appears this logs all nodetool commands whether they parse correctly or not. Is that what
you want? or should this printHistory occur after command = cmd.getCommand(); ?


would be nice if the trunk version used try-with-resources

                
> nodetool history logging
> ------------------------
>
>                 Key: CASSANDRA-5823
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5823
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jason Brown
>            Assignee: Jason Brown
>            Priority: Minor
>             Fix For: 1.2.8, 2.0 rc1
>
>         Attachments: 5823-v1.patch
>
>
> Capture the commands and time executed from nodetool into a log file, similar to the
cli.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message