Thanks for the information.
George.
On Wed, Apr 10, 2019 at 3:14 AM Alok Dwivedi
wrote:
> Your delete query
>
> "DELETE FROM myTable WHERE course_id = 'C' AND assignment_id = 'A1';”.
>
> will generate multi row range tombstones. Since you are reading entire
> partition which effectively will be
Your delete query
>> "DELETE FROM myTable WHERE course_id = 'C' AND assignment_id = 'A1';”.
will generate multi row range tombstones. Since you are reading entire
partition which effectively will be read in pages (slice query equivalent) you
may get tombstones in certain pages depending upon how
Normal deletes are fine.
Sadly there's a lot of hand wringing about tombstones in the generic
sense which leads people to try to work around *every* case where
they're used. This is unnecessary. A tombstone over a single row
isn't a problem, especially if you're only fetching that one row back.
Hi,
I have a table defined like this:
CREATE TABLE myTable (
course_id text,
assignment_id text,
assignment_item_id text,
data text,
boolean active,
PRIMARY KEY (course_id, assignment_id, assignment_item_id)
);
i.e. course_id as the partition key and assignment_id, assignment_item_id
as clusterin
