Thanks, it makes perfect sense now. Well an option in cassandra could
make it optional
as far as display it concerned, w/o performance hit -- of course this is
all unimportant.
Thanks again
Maxim
On 12/14/2011 11:30 AM, Brandon Williams wrote:
http://wiki.apache.org/cassandra/FAQ#range_ghos
http://wiki.apache.org/cassandra/FAQ#range_ghosts
On Wed, Dec 14, 2011 at 4:36 AM, Radim Kolar wrote:
> Dne 14.12.2011 1:15, Maxim Potekhin napsal(a):
>
>> Thanks. It could be hidden from a human operator, I suppose :)
>
> I agree. Open JIRA for it.
Dne 14.12.2011 1:15, Maxim Potekhin napsal(a):
Thanks. It could be hidden from a human operator, I suppose :)
I agree. Open JIRA for it.
Thanks. It could be hidden from a human operator, I suppose :)
On 12/13/2011 7:12 PM, Harold Nguyen wrote:
Hi Maxim,
The reason for this is because if node 1 goes down while you deleted
information on node 2, node 1 will know not to repair the data when it comes
back again. It will know th
Hi Maxim,
The reason for this is because if node 1 goes down while you deleted
information on node 2, node 1 will know not to repair the data when it comes
back again. It will know that an operation has been performed to delete the
data.
Harold
-Original Message-
From: Maxim Potekhi
The cli's 'list' command is the same as get_range_slices(), which is the
one type of query where you can get back range ghosts (deleted keys).
On Tue, Dec 13, 2011 at 6:02 PM, Maxim Potekhin wrote:
> Hello,
>
> I searched the archives and it appears that this question was once asked
> but
> was
