[jira] [Commented] (CASSANDRA-6745) Require specifying rows_per_partition_to_cache

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

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

Sylvain Lebresne commented on CASSANDRA-6745:
---------------------------------------------

On that note, I have wondered if it wouldn't be cleaner to group the caching options into a map like we do for say compression options. Something like:
{noformat}
ALTER t WITH caching = { 'keys' : 'false', 'rows' : 'true', 'rows_per_partition' : '100' }
{noformat}
This feels cleaner to me, and would provide a clear home for future other caching options (or if say, we start moving some of your global ones to per-table ones).

> 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.1.5#6160)