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 cases, and will be less adequate going forward.
On Thu, Jul 1, 2010 at 9:08 AM, Jonathan Ellis <jbel...@gmail.com> wrote: > On Thu, Jul 1, 2010 at 6:44 AM, Jools <jool...@gmail.com> 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, Apache Cassandra > co-founder of Riptano, the source for professional Cassandra support > http://riptano.com >
