Thanks Jeff for the information. On Wed, 10 Nov 2021 at 21:08, Jeff Jirsa <jji...@gmail.com> wrote:
> This type of delete - which doesnt supply a user_id, so it's deleting a > range of rows - creates what is known as a range tombstone. It's not tied > to any given cell, as it covers a range of cells, and supersedes/shadows > them when merged (either in the read path or compaction path). > > > > On Wed, Nov 10, 2021 at 4:27 AM raman gugnani <ramangugnani....@gmail.com> > wrote: > >> HI Team, >> >> >> I have one table below and want to delete data on this table. >> >> >> DELETE FROM game.tournament USING TIMESTAMP 1616925780000000 WHERE >> tournament_id = 1 AND version_id = 1 AND partition_id = 1; >> >> >> Cassandra internally manages the timestamp of each column when some data >> is updated on the same column. >> >> >> My Query is , *USING TIMESTAMP 1616925780000000* picks up a timestamp of >> which column ? >> >> >> >> CREATE TABLE game.tournament ( >> >> tournament_id bigint, >> >> version_id bigint, >> >> partition_id bigint, >> >> user_id bigint, >> >> created_at timestamp, >> >> rank bigint, >> >> score bigint, >> >> updated_at timestamp, >> >> PRIMARY KEY ((tournament_id, version_id, partition_id), user_id) >> >> ) WITH CLUSTERING ORDER BY (user_id ASC) >> >> >> >> >> >> >> >> -- >> Raman Gugnani >> > -- Raman Gugnani
