You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/10/21 17:45:42 UTC

[jira] [Resolved] (CASSANDRA-6105) Cassandra Triggers to execute on replicas

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

Jonathan Ellis resolved CASSANDRA-6105.
---------------------------------------

    Resolution: Won't Fix

> Cassandra Triggers to execute on replicas
> -----------------------------------------
>
>                 Key: CASSANDRA-6105
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6105
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Michael
>            Priority: Minor
>
> We would like to keep ElasticSearch eventually consistent across data centers while keeping ElasticSearch clusters local to each data center. The idea is, utilize Cassandra to replicate data across data centers and use triggers to kick off an event which would populate data into ElasticSearch Clusters. Thus keeping disperse ElasticSearch clusters eventually consistent while not extending ElasticSearch across data centers. 
> That in mind, it would be very useful if a trigger could be made to execute on every replica. Or at least one replica per data center.



--
This message was sent by Atlassian JIRA
(v6.1#6144)