-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kv: consider splitting at tenant's end key range boundary #92072
Copy link
Copy link
Closed
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Description
See slack thread for context: https://cockroachlabs.slack.com/archives/C0KB9Q03D/p1667393625502529
Today, each tenant's end key (in the range list) is the first key of the next tenant (i.e. the last key of tenant 10 is /tenant/30, if only tenants 10 and 30 are defined). For the the last tenant its end key is /Max.
We'd like all this to be /Tenant/<id>/<endprefix>.
This causes a few concerns around things like zone configs from the previous tenant temporarily leaking into a newly created tenant. This should be straightforward to address, so we should.
cc @knz @cockroachdb/multi-tenant
Jira issue: CRDB-21562
Epic CRDB-23344
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)