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

Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2016/01/21 16:28:39 UTC

[jira] [Updated] (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 ]

Marcus Eriksson updated CASSANDRA-11056:
----------------------------------------
    Assignee: Björn Hegerfors

assigning [~Bj0rn] - if you don't have time for this, let me know

I think the biggest task here is to make sure nothing explodes for users upgrading to this

> Use max timestamp to decide DTCS-timewindow-membership
> ------------------------------------------------------
>
>                 Key: CASSANDRA-11056
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11056
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Björn Hegerfors
>
> 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)