You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jon Haddad (JIRA)" <ji...@apache.org> on 2016/12/02 21:27:58 UTC

[jira] [Resolved] (CASSANDRA-11056) Use max timestamp to decide DTCS-timewindow-membership

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

Jon Haddad resolved CASSANDRA-11056.
------------------------------------
    Resolution: Won't Fix

> Use max timestamp to decide DTCS-timewindow-membership
> ------------------------------------------------------
>
>                 Key: CASSANDRA-11056
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11056
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Compaction
>            Reporter: Marcus Eriksson
>            Assignee: Björn Hegerfors
>              Labels: dtcs
>         Attachments: cassandra-2.2-CASSANDRA-11056.txt
>
>
> TWCS (CASSANDRA-9666) uses max timestamp to decide time window membership, we should do the same in DTCS so that users can configure DTCS to work exactly like TWCS



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