Re: Keys for deleted rows visible in CLI
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.
Re: Keys for deleted rows visible in CLI
http://wiki.apache.org/cassandra/FAQ#range_ghosts On Wed, Dec 14, 2011 at 4:36 AM, Radim Kolar h...@sendmail.cz 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.
Re: Keys for deleted rows visible in CLI
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_ghosts On Wed, Dec 14, 2011 at 4:36 AM, Radim Kolarh...@sendmail.cz 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.
Keys for deleted rows visible in CLI
Hello, I searched the archives and it appears that this question was once asked but was not answered. I just deleted a lot of rows, and want to list in cli. I still see the keys. This is not the same as getting slices, is it? Anyhow, what's the reason and rationale? I run 0.8.8. Thanks Maxim
Re: Keys for deleted rows visible in CLI
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 potek...@bnl.gov wrote: Hello, I searched the archives and it appears that this question was once asked but was not answered. I just deleted a lot of rows, and want to list in cli. I still see the keys. This is not the same as getting slices, is it? Anyhow, what's the reason and rationale? I run 0.8.8. Thanks Maxim -- Tyler Hobbs DataStax http://datastax.com/
RE: Keys for deleted rows visible in CLI
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 Potekhin [mailto:potek...@bnl.gov] Sent: Tuesday, December 13, 2011 4:03 PM To: user@cassandra.apache.org Subject: Keys for deleted rows visible in CLI Hello, I searched the archives and it appears that this question was once asked but was not answered. I just deleted a lot of rows, and want to list in cli. I still see the keys. This is not the same as getting slices, is it? Anyhow, what's the reason and rationale? I run 0.8.8. Thanks Maxim 'Like' us on Facebook for exclusive content and other resources on all Barracuda Networks solutions. Visit http://barracudanetworks.com/facebook
Re: Keys for deleted rows visible in CLI
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 that an operation has been performed to delete the data. Harold -Original Message- From: Maxim Potekhin [mailto:potek...@bnl.gov] Sent: Tuesday, December 13, 2011 4:03 PM To: user@cassandra.apache.org Subject: Keys for deleted rows visible in CLI Hello, I searched the archives and it appears that this question was once asked but was not answered. I just deleted a lot of rows, and want to list in cli. I still see the keys. This is not the same as getting slices, is it? Anyhow, what's the reason and rationale? I run 0.8.8. Thanks Maxim 'Like' us on Facebook for exclusive content and other resources on all Barracuda Networks solutions. Visit http://barracudanetworks.com/facebook
