[jira] [Resolved] (CASSANDRA-8453) Ability to override TTL on different data-centers, plus one-way replication

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

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

Aleksey Yeschenko resolved CASSANDRA-8453.
------------------------------------------
    Resolution: Not a Problem

Right.

If you somehow manage to do it your way, on reads the digest would mismatch (ttl is part of the digest calculation) and read repair will sync the data. Same regarding explicit repair.

Either you go with writing the same data to several separate keyspaces - with TTL to one, without TTL to another, and only have the non-ttl keyspace in one DC, or, well, there is no other way.

> Ability to override TTL on different data-centers, plus one-way replication
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8453
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8453
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>            Reporter: Jacques-Henri Berthemet
>
> Here is my scenario:
> I want to have one datacenter specialized for operations "DCO" and another for historical/audit "DCH". Replication will be used between DCO and DCH.
> When TTL expires on DCO and data is deleted I'd like the data on DCH to be kept for other purposes. Ideally a different TTL could be set in DCH.
> I guess this also implies that replication should be done only in DCO => DCH direction so that data is not re-created. But that's secondary, DCH data is not meant to be modified.
> Is this kind of feature feasible for future versions of Cassandra? If not, would you have some pointers to modify Cassandra in order to achieve this functionality?
> Thank you.



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