> The problems occurs during the day where updates can be sent that possibly
> contain older data then the nightly batch update.
If you have a an application level sequence for updates (I used that term to
avoid saying timestamp) you could use it as the cassandra timestamp. As long as
you know
, 2010 2:02 PM
To: user
Subject: Re: Design Question
Hi Mubarak,
Did you see David Strauss's talk on queing at the Summit?
http://riptano.blip.tv/file/4015190/
What specifics can you give as to how your use case is similar to /
different from what David covered?
On Sun, Nov 7, 2010 at 7:
Is the slide deck for this presentation online somewhere?
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Monday, November 08, 2010 2:02 PM
To: user
Subject: Re: Design Question
Hi Mubarak,
Did you see David Strauss's talk on queing at the Summit?
Hi Mubarak,
Did you see David Strauss's talk on queing at the Summit?
http://riptano.blip.tv/file/4015190/
What specifics can you give as to how your use case is similar to /
different from what David covered?
On Sun, Nov 7, 2010 at 7:05 PM, Mubarak Seyed wrote:
> Hi All,
> Can someone please v
FWIW I would recommend first trying to solve the issue in your application rather than with Cages or Zoo Keeper. Although I do not have experience with Cages or Zoo Keeper, it's another major server component in your stack.If you really do have a queue and multiple simultaneous readers consider usi
If you go the home-grown route, check out these musings on adapting
Lamport's Bakery algorithm to a similar problem:
http://wiki.apache.org/cassandra/Locking
On Sun, Nov 7, 2010 at 5:05 PM, Mubarak Seyed wrote:
> Hi All,
> Can someone please validate and recommend a solution for the given design
