Hi,
Just trying out Cassandra (0.5), looks great so far but I've got a
question about removing data:
For my test suite I would like to be able to build-up data in the
database and then have the test framework tear it all back down
again. Trouble is, if I do a batch_insert, remove, batch_insert (o
Hi,
To summarise my app;
* try to get item from UserUrl cf
* if not found then check in the Url cf to see if we have fetched
url before and add to UserUrl.
* else, fetch the url and its details put in Url and UserUrl
The unit tests covering this shouldn't hit the else as they put wha
At Wed, 7 Apr 2010 17:29:49 +0200,
Sylvain Lebresne wrote:
>
> Use ConsistencyLevel.QUORUM when you write *and* when you read.
I already do (plus, I only test with one node).
BTW, I'm on 0.5.0, if that makes any difference.
Cheers,
Phil
At Wed, 07 Apr 2010 13:19:26 -0700,
Mike Gallamore wrote:
>
> I have writes to cassandra that are failing, or at least a read shortly
> after a write is still getting an old value. I realize Cassandra is
> "eventually consistent" but this system is a single CPU single node with
> consistency le
At Thu, 08 Apr 2010 11:41:30 -0700,
Mike Gallamore wrote:
>
> [1 ]
> On 04/08/2010 04:53 AM, Philip Jackson wrote:
> > At Wed, 07 Apr 2010 13:19:26 -0700,
> > Mike Gallamore wrote:
> >
> >> I have writes to cassandra that are failing, or at least a read
