Re: Listeners and remote Graphs.

Yeah, but I am not certain that Cassandra will return them in the "right order". I have to delve into that a bit more. On Thu, Jan 12, 2017 at 10:48 AM, Andy Seaborne wrote: > > > On 11/01/17 12:24, Claude Warren wrote: > >> Cassandra does not support transactions. However, I

Re: Listeners and remote Graphs.

On 11/01/17 12:24, Claude Warren wrote: Cassandra does not support transactions. However, I can see the use for a bounding construct that indicates "all these triples were added/deleted." The original driver for the Cassandra implementation was that we needed one for a use case at work.

Re: Listeners and remote Graphs.

To be honest, I was thinking that if the graph notification for the cassandra graph needed to notify all the attached graph implementations of changes I would use Kafka or other similar pluggable Queue to do the notification. Claude On Wed, Jan 11, 2017 at 2:48 PM, A. Soroka

Re: Listeners and remote Graphs.

Cassandra does not support transactions. However, I can see the use for a bounding construct that indicates "all these triples were added/deleted." The original driver for the Cassandra implementation was that we needed one for a use case at work. However, Cassandra is generally about speed of

Re: Listeners and remote Graphs.

Hi Claude, On 09/01/17 19:22, Claude Warren wrote: Greetings, Given that the Cassandra server can host multiple client and those clients can open the same graph on the server simultaneously. Basically two updatable synchronized views on one data set. Assume graph A is opened on client X

Listeners and remote Graphs.

Greetings, Given that the Cassandra server can host multiple client and those clients can open the same graph on the server simultaneously. Basically two updatable synchronized views on one data set. Assume graph A is opened on client X and client Y and applications at X and Y both register