cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jackson Chung (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-2983) CliClient print memtable threshold in incorrect order
Date Mon, 01 Aug 2011 23:16:27 GMT
CliClient print memtable threshold in incorrect order
-----------------------------------------------------

                 Key: CASSANDRA-2983
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2983
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 0.8.2
            Reporter: Jackson Chung
            Priority: Minor


as a continuation from #2839 looks like it was incorrectly merged into 0.8 as well, hence
affecting > 0.8.2.

for trunk, this is also changed (time is taken out). So I guess format wise, we would stick
with the fixed format in 0.7.7 per #2839 , which is:

{code}
sessionState.out.printf("      Memtable thresholds: %s/%s/%s (millions of ops/minutes/MB)%n",
    cf_def.memtable_operations_in_millions, cf_def.memtable_flush_after_mins, cf_def.memtable_throughput_in_mb);
{code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message