cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques-Henri Berthemet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8453) Ability to override TTL on different data-centers, plus one-way replication
Date Wed, 10 Dec 2014 14:07:13 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241118#comment-14241118
] 

Jacques-Henri Berthemet commented on CASSANDRA-8453:
----------------------------------------------------

Do you know which class receives/sends the replication messages from other DCs?

> 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)

Mime
View raw message