cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6745) Require specifying rows_per_partition_to_cache
Date Mon, 03 Mar 2014 17:43:22 GMT

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

Marcus Eriksson commented on CASSANDRA-6745:
--------------------------------------------

My reasoning was that it made no real sense to first have a boolean and then state how many
rows, felt like i was repeating myself when doing it, but I can buy the argument that if we
want to extend this in the future, having the bools might make sense

And the thrift part, sure

> Require specifying rows_per_partition_to_cache
> ----------------------------------------------
>
>                 Key: CASSANDRA-6745
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6745
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Marcus Eriksson
>            Priority: Trivial
>             Fix For: 2.1 beta2
>
>
> We should require specifying rows_to_cache_per_partition for new tables or newly ALTERed
when row caching is enabled.
> Pre-upgrade should be grandfathered in as ALL to match existing semantics.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message