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

Olivier Michallat updated CASSANDRA-15604:
------------------------------------------
    Description: 
CASSANDRA-13910 removed the {{read_repair_chance}} and 
{{dclocal_read_repair_chance}} options for tables and materialized views.

CASSANDRA-12868 made {{default_time_to_live}} illegal for materialized views.

However the corresponding columns still exist in {{system_schema.tables}} and 
{{system_schema.views}}. Maybe it would make sense to remove them in Cassandra 
4. Historically, obsolete options have been removed in similar cases, for 
example {{compaction_strategy_class}}, {{compaction_strategy_options}} and 
{{compression_parameters}} were present in 2.2 but removed in 3.0 (arguably 
there was also a major refactoring of schema tables during that transition).

This is not a huge deal, but it would make things a bit easier for the Java 
driver (our metadata exposes a "client-side describe" feature, and currently we 
assume that any column in the schema table must be added to the CREATE TABLE 
statement).

  was:
CASSANDRA-13910 removed the {{read_repair_chance}} and 
{{dclocal_read_repair_chance}} options for tables and materialized views.

CASSANDRA-12868 made {{default_time_to_live}} illegal for materialized views.

However the corresponding columns still exist in {{system_schema.tables}} and 
{{system_schema.views}}. Maybe it would make sense to remove them in Cassandra 
4. Historically, obsolete options have been removed in similar cases, for 
example {{compaction_strategy_class}}, {{compaction_strategy_options}} and 
{{compression_parameters}} in Cassandra 2.2 => 3 (arguably there was also a 
major refactoring of schema tables during that transition).

This is not a huge deal, but it would make things a bit easier for the Java 
driver (our metadata exposes a "client-side describe" feature, and currently we 
assume that any column in the schema table must be added to the CREATE TABLE 
statement).


> Remove obsolete table/MV options from schema tables
> ---------------------------------------------------
>
>                 Key: CASSANDRA-15604
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15604
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Olivier Michallat
>            Priority: Normal
>
> CASSANDRA-13910 removed the {{read_repair_chance}} and 
> {{dclocal_read_repair_chance}} options for tables and materialized views.
> CASSANDRA-12868 made {{default_time_to_live}} illegal for materialized views.
> However the corresponding columns still exist in {{system_schema.tables}} and 
> {{system_schema.views}}. Maybe it would make sense to remove them in 
> Cassandra 4. Historically, obsolete options have been removed in similar 
> cases, for example {{compaction_strategy_class}}, 
> {{compaction_strategy_options}} and {{compression_parameters}} were present 
> in 2.2 but removed in 3.0 (arguably there was also a major refactoring of 
> schema tables during that transition).
> This is not a huge deal, but it would make things a bit easier for the Java 
> driver (our metadata exposes a "client-side describe" feature, and currently 
> we assume that any column in the schema table must be added to the CREATE 
> TABLE statement).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to