[jira] [Resolved] (CASSANDRA-11350) Max_SSTable_Age isn't really deprecated in DTCS

["Marcus Eriksson (JIRA)" <ji...@apache.org>]

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

Marcus Eriksson resolved CASSANDRA-11350.
-----------------------------------------
    Resolution: Not A Problem

closing as not a problem - better to ask the mailing lists for clarification of these things

> Max_SSTable_Age isn't really deprecated in DTCS
> -----------------------------------------------
>
>                 Key: CASSANDRA-11350
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11350
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction
>         Environment: PROD
>            Reporter: Anubhav Kale
>            Priority: Minor
>
> Based on the comments in https://issues.apache.org/jira/browse/CASSANDRA-10280, and changes made to DateTieredCompactionStrategyOptions.java, the Max_SSTable_Age field is marked as deprecated.
> However, this is still used to filter the old SS Tables in DateTieredCompactionStrategy.java. Once those tables are filtered, Max_Window_Size is used to limit how back in time we can go (essentially how Max_SSTable_Age was used previously).
> So I am somewhat confused on the exact use of these two fields. Should Max_SSTable_Age be really removed and Max_Window_Size be used to filter old tables (in which case it should be set to 1 year as well) ?
> Currently, Max_SSTable_Age = 1 Year, and Max_Window_Size = 1 Day. What is the expected behavior with these settings ?



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