Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[colocation] Make reads aware of table-level tombstone #3359

Closed
jaki opened this issue Jan 15, 2020 · 0 comments
Closed

[colocation] Make reads aware of table-level tombstone #3359

jaki opened this issue Jan 15, 2020 · 0 comments
Assignees
Labels
area/docdb YugabyteDB core features area/ysql Yugabyte SQL (YSQL)

Comments

@jaki
Copy link
Contributor

jaki commented Jan 15, 2020

Reads from SELECTs and point UPDATEs on a colocated table should be aware of table-level tombstones denoting the deletion of tables. Timestamps should be taken into account such that rows at a hybrid time earlier than the table-level tombstone are considered deleted. For example, a TRUNCATE TABLE followed by a SELECT on a colocated table should not surface the old values.

This is step 3 of 4 for the data deletion of the drop flow, issue #3035.

@jaki jaki added the area/ysql Yugabyte SQL (YSQL) label Jan 15, 2020
@jaki jaki self-assigned this Jan 15, 2020
@jaki jaki added the area/docdb YugabyteDB core features label Jan 30, 2020
@jaki jaki closed this as completed in f6f4173 Feb 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features area/ysql Yugabyte SQL (YSQL)
Projects
None yet
Development

No branches or pull requests

1 participant