Re: Identifying Tombstones

2010-07-01 Thread Jonathan Shook
Or the same key, in some cases. If you have multiple operations against the same columns 'at the same time', they ordering may be indefinite. This can happen if the effective resolution of your time stamp is coarse enough to bracket multiple operations. Milliseconds are not fine enough in many case

Re: Identifying Tombstones

2010-07-01 Thread Jonathan Ellis
On Thu, Jul 1, 2010 at 6:44 AM, Jools wrote: > Should you try to write to the same column family using the same key as a > tombstone, it will be silently ignored. Only if you perform the write with a lower timestamp than the delete you previously performed. -- Jonathan Ellis Project Chair, Apac

Re: Identifying Tombstones

2010-07-01 Thread Jonathan Ellis
http://wiki.apache.org/cassandra/FAQ#range_ghosts On Thu, Jul 1, 2010 at 6:35 AM, Phil Stanhope wrote: > I understand that tombstones are internal implementation detail ... yet, the > fact remains in 0.6.2 that a key/col creation followed by a delete of the > key/col will result in the key being

Re: Identifying Tombstones

2010-07-01 Thread Jools
Just a short note to add If you delet a key, and it has not been removed via a flush and compaction, it will be returned as a key with no (super)column(s) from a get_range_slices call. Should you try to write to the same column family using the same key as a tombstone, it will be silently ign

Re: Identifying Tombstones

2010-07-01 Thread Phil Stanhope
I understand that tombstones are internal implementation detail ... yet, the fact remains in 0.6.2 that a key/col creation followed by a delete of the key/col will result in the key being returned in a get_range_slices call. If the CF is flushed and compacted (after GCGraceSeconds), the key will

Re: Identifying Tombstones

2010-07-01 Thread David Boxenhorn
Great! Thanks! On Thu, Jul 1, 2010 at 3:40 PM, Jonathan Ellis wrote: > Tombstones are internal to Cassandra and are never sent to the client. > > On Thu, Jul 1, 2010 at 2:20 AM, David Boxenhorn wrote: > > I recently learned that when I get a key, I might get a tombstone. > > > > How can I know

Re: Identifying Tombstones

2010-07-01 Thread Jonathan Ellis
Tombstones are internal to Cassandra and are never sent to the client. On Thu, Jul 1, 2010 at 2:20 AM, David Boxenhorn wrote: > I recently learned that when I get a key, I might get a tombstone. > > How can I know if a returned key is a tombstone? (I need to ignore them for > my application.) >

Identifying Tombstones

2010-07-01 Thread David Boxenhorn
I recently learned that when I get a key, I might get a tombstone. How can I know if a returned key is a tombstone? (I need to ignore them for my application.)