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

Yuki Morishita commented on CASSANDRA-4088:
-------------------------------------------

+1.

I created following tables in 1.0.8:

{noformat}
CREATE TABLE Test1 (key int PRIMARY KEY) WITH row_cache_size = 1 AND 
key_cache_size = 1;
CREATE TABLE Test2 (key int PRIMARY KEY) WITH row_cache_size = 0 AND 
key_cache_size = 0;
CREATE TABLE Test3 (key int PRIMARY KEY) WITH row_cache_size = 1;
CREATE TABLE Test4 (key int PRIMARY KEY) WITH key_cache_size = 1;
CREATE TABLE Test5 (key int PRIMARY KEY);
CREATE TABLE Test6 (key int PRIMARY KEY) WITH row_cache_size = 1 AND 
key_cache_size = 0;
{noformat}

and got following in patched 1.1:

{noformat}
create column family Test1
  ...
  and caching = 'ALL';
create column family Test2
  ...
  and caching = 'NONE';
create column family Test3
  ...
  and caching = 'ALL';
create column family Test4
  ...
  and caching = 'KEYS_ONLY';
create column family Test5
  ...
  and caching = 'KEYS_ONLY';
create column family Test6
  ...
  and caching = 'ROWS_ONLY';
{noformat}
                
> Respect 1.0 cache settings as much as possible when upgrading
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-4088
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4088
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.1.0
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>             Fix For: 1.1.0
>
>         Attachments: CASSANDRA-4088.patch
>
>
> When converting a 1.0 schema to 1.1, we should look at the key and row caches 
> (just whether they are en- or dis-abled) and set the caching setting 
> accordingly.  I think right now upgrading means all your row caching is gone 
> until you update it manually.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to