cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CASSANDRA-2043) remove memtable throughput configuration
Date Wed, 26 Jan 2011 02:24:44 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-2043.
---------------------------------------

    Resolution: Won't Fix
      Assignee:     (was: Jon Hermes)

having the two settings is still useful for CFs with high variance in column value sizes.

> remove memtable throughput configuration
> ----------------------------------------
>
>                 Key: CASSANDRA-2043
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2043
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>             Fix For: 0.8
>
>
> Now that we can set memtable thresholds on a per-CF basis, having two sizing thresholds
is more confusing than helpful, especially for new users who see the throughput threshold
and think that it accurately represents how much memory a memtable will use

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message