how to avoid range ghosts?

[Satoshi Yamada <bi...@yahoo.co.jp>]

Hi,
What is the recommended way to avoid range ghost in using get_range()?In my case, order of the key is not problem. It seems valid to use random :start_key in every query, but i'm new to cassandra and do not know if it'srecommended or not.
I use Cassandra 1.1.4 and ruby client. Range ghosts happens when oneprocess keeps on inserting data while other process get_range and deletethem.
thanks in advance,satoshi

Re: how to avoid range ghosts?

[Edward Capriolo <ed...@gmail.com>]

Read this:

http://wiki.apache.org/cassandra/FAQ#range_ghosts

Then say this to yourself:

http://cn1.kaboodle.com/img/b/0/0/196/4/AAAAC1xHoQAAAAAAAZZL9w/ghostbusters-logo-i-aint-afraid-of-no-ghost-pinback-button-1.25-pin-badge.jpg?v=1320511953000

On Sun, Oct 7, 2012 at 4:15 AM, Satoshi Yamada
<bi...@yahoo.co.jp>wrote:

> Hi,
>
> What is the recommended way to avoid range ghost in using get_range()?
> In my case, order of the key is not problem. It seems valid to use random
>  :start_key in every query, but i'm new to cassandra and do not know if
> it's
> recommended or not.
>
> I use Cassandra 1.1.4 and ruby client. Range ghosts happens when one
> process keeps on inserting data while other process get_range and delete
> them.
>
> thanks in advance,
> satoshi
>