search

coherence-community / coherence-incubator

Coherence Incubator
38 stars 37 forks source link

Introduce support for using lite-transactions with Push Replication #131

Closed brianoliver closed 9 years ago

brianoliver commented 9 years ago

Currently push replication / event distribution doesn't take into account entries updates as part of a "lite-transaction".

While updates occur in-order, the destination (Event Channel) may need to know the boundaries of the "lite-transactions" and/or process all of the changes in a "lite-transaction", including resolving conflicts.

To achieve this we need to introduce a Live Event-based Interceptor to capture and perform replication, instead of using the existing Push Replication CacheStore.

To support this we may need to add transactional event support to the EventDistribution framework. eg: TransactionLiteCacheEvent and then DistributableTransactionLiteCacheEvent

We may also need a mechanism to order the manner in which entries in a lite transaction are applied to a remote cache, specifically to avoid dead-locking remote caches.

brianoliver commented 9 years ago

@brianoliver said: With the release of Coherence 12.2.1 (including Federated Caching) imminent, there's little reason to implement this as Coherence itself will naturally support this capability.

brianoliver commented 8 years ago

This issue was imported from JIRA COHINC-131

brianoliver commented 9 years ago

Reported by @brianoliver

brianoliver commented 9 years ago

Marked as won't fix by @brianoliver on Wednesday, August 19th 2015, 11:14:35 am