On Tue, Apr 6, 2010 at 2:12 PM, Steve wrote:
...
> Should I assume that it isn't common practice to write updates
> atomically in-real time, and batch process them 'off-line' to increase
> the atomic granularity? It seems an obvious strategy... possibly one
> for which an implementation might use
On 06/04/2010 21:40, Benjamin Black wrote:
> I suggest the reasons you list (which are certainly great reasons!)
> are also the reasons there is no referential integrity or transaction
> support.
Quite. I'm not trying to make recommendations for how Cassandra should
be changed to be more like a
I suggest the reasons you list (which are certainly great reasons!)
are also the reasons there is no referential integrity or transaction
support. It seems the common practice of using a system like
Zookeeper for the synchronization parts alongside Cassandra would be
applicable here. Have you inv
On 06/04/2010 18:53, Tatu Saloranta wrote:
>> I've read all about QUORUM, and it is generally useful, but as far as I
>> can tell, it can't give me a transaction...
>>
> Correct. Only individual operations are atomic, and ordering of
> insertions is not guaranteed.
>
As I thought.
> I think
On 06/04/2010 18:50, Benjamin Black wrote:
> I'm finding this exchange very confusing. What exactly about
> Cassandra 'looks absolutely ideal' to you for your project? The write
> performance, the symmetric, peer to peer architecture, etc?
>
Reasons I like Cassandra for this project:
* C
On Tue, Apr 6, 2010 at 10:12 AM, Steve wrote:
> On 06/04/2010 15:26, Eric Evans wrote:
...
> I've read all about QUORUM, and it is generally useful, but as far as I
> can tell, it can't give me a transaction...
Correct. Only individual operations are atomic, and ordering of
insertions is not guar
I'm finding this exchange very confusing. What exactly about
Cassandra 'looks absolutely ideal' to you for your project? The write
performance, the symmetric, peer to peer architecture, etc?
b
On 06/04/2010 15:26, Eric Evans wrote:
> On Tue, 2010-04-06 at 12:00 +0100, Steve wrote:
>
>> First, I apologise sending this to the 'dev' mailing list - I couldn't
>> find one for Cassandra users - and also for the basic nature of my
>> questions...
>>
> user@cassandra.apache.org, (follow-
On Tue, 2010-04-06 at 12:00 +0100, Steve wrote:
> First, I apologise sending this to the 'dev' mailing list - I couldn't
> find one for Cassandra users - and also for the basic nature of my
> questions...
user@cassandra.apache.org, (follow-ups there).
> I'm trying to get my head around the possib
