[
https://issues.apache.org/jira/browse/CASSANDRA-12868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654751#comment-15654751
]
Sundar Srinivasan commented on CASSANDRA-12868:
-----------------------------------------------
I am new to Cassandra, although I have some experience developing proprietary
distributed systems. When I used Cassandra, I liked it. When I started reading
its architecture and code, I loved it. I am trying to fix this one by
disallowing TTL for creation of materialized views and get my hands dirty with
the code.
Just to get some direction, is this the correct place where the fix should be?
CreateViewStatement::announceMigration()
I generally use Emacs for coding. Do you guys have any instruction manual on
how to start a JDB session for this? Like JVM argument etc.
> MV creation allows a 'default_time_to_live' option, but ignores it
> ------------------------------------------------------------------
>
> Key: CASSANDRA-12868
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12868
> Project: Cassandra
> Issue Type: Bug
> Reporter: Srinivasarao Daruna
> Priority: Minor
> Labels: lhf
>
> 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;
> The queries are accepted in CQL. As per the detail, it should use 30 seconds
> for Materialized view and 60 seconds for parent table.
> But, it is always 60 seconds (as the parent table)
> 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)
