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] [Updated] (CASSANDRA-7193) rows_per_partition_to_cache is not reflected in table DESCRIBE
Date Mon, 12 May 2014 06:42:15 GMT

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

Marcus Eriksson updated CASSANDRA-7193:
---------------------------------------

    Attachment: 0001-remove-rows_per_partition_to_cache.patch

the correct syntax is "WITH caching = {'keys': 'NONE', 'rows_per_parti
tion': 'ALL'};"

attached patch removes leftover rows_per_partition_to_cache keyword

> rows_per_partition_to_cache is not reflected in table DESCRIBE
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-7193
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7193
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ryan McGuire
>            Assignee: Marcus Eriksson
>            Priority: Minor
>         Attachments: 0001-remove-rows_per_partition_to_cache.patch
>
>
> I can create a table with the new query cache from CASSANDRA-5357:
> {code}
> CREATE TABLE status (user text, status_id timeuuid, status text, PRIMARY KEY (user, status_id))
WITH caching = '{"keys":"ALL", "rows_per_partition":"10"}';
> {code}
> This method appears to work fine.
> However, that is not the syntax mentioned in that ticket. It says to use a rows_per_partition_to_cache
setting instead, which does appear to work in cql:
> {code}
> CREATE TABLE status2 (user text, status_id timeuuid, status text, PRIMARY KEY (user,
status_id)) WITH rows_per_partition_to_cache = 200;
> {code}
> But that setting is not reflected in the table description, instead it still shows NONE:
> {code}
> cqlsh:test> DESCRIBE TABLE status2;
> CREATE TABLE test.status2 (
>     user text,
>     status_id timeuuid,
>     status text,
>     PRIMARY KEY (user, status_id)
> ) WITH CLUSTERING ORDER BY (status_id ASC)
>     AND caching = '{"keys":"ALL", "rows_per_partition":"NONE"}'
>     ...
> {code}
> Similarly, alter table with that syntax, does not produce an error, but also does not
seem to affect the setting :
> {code}
> ALTER TABLE test.status WITH rows_per_partition_to_cache = 200;
> {code}



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

Mime
View raw message