cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srinivasarao Daruna (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-12868) Cassandra Materialized views cannot be created with TTL different to parent table
Date Wed, 02 Nov 2016 00:42:58 GMT
Srinivasarao Daruna created CASSANDRA-12868:
-----------------------------------------------

             Summary: Cassandra Materialized views cannot be created with TTL different to
parent table
                 Key: CASSANDRA-12868
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12868
             Project: Cassandra
          Issue Type: Wish
            Reporter: Srinivasarao Daruna


Hi,

By default, materialized views are using the TTL of primary table, irrespective of the configured
value provided in materialized view creation.

For eg:

table:

CREATE TABLE test2(id text, date text, col1 text,col2 text, PRIMARY KEY(id,date)) WITH default_time_to_live
= 60 AND CLUSTERING ORDER BY (date DESC);

CREATE MATERIALIZED VIEW test3_view AS
SELECT id, date, col1
FROM test3 
WHERE id IS NOT NULL AND date IS NOT NULL
PRIMARY KEY(id,date) WITH default_time_to_live = 30;

case 1: 
parent table and materialized view with different TTL
MV will always have the TTL of parent.

case 2:
Parent table without TTL but materialized view with TTL
MV does not have the TTL even though the configuration has been accepted in the table creation.

Expected:
Either the TTL configuration should not be accepted in the materialized view creation, if
it is of no value.

Or

TTL has to be applied differently for both Materialized View and Table if the configuration
is added.

If no configuration, TTL has to be taken from the parent table. 





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message