Are you re-using the timestamp from the first insert on the second insert?
The insert must occur after the tombstone, otherwise cassandra will assume the tombstone is the current version and ignore the delete.
On 01 Oct, 2010,at 10:25 AM, Peter Harrison <firstname.lastname@example.org> wrote:
If you delete a row, and it therefore is marked as tombstone, and
subsequently you try to insert the row again it appears to succeed,
but if you try to request the row you don't get a result.
If you try to insert a row that has been recently deleted, and has an
active tombstone I would expect either the tombstone marker to be
removed, or the insert to fail. It seems to currently accept the
insert and then subsequently the row can't be found.