cockroachdb / cockroachdb/cockroach
storage: fallout from UA's per-tenant cluster versions
Open
A-storage
C-cleanup
T-storage
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
The storage engine often uses cluster versions for migrations and to impose restrictions on clients. There's new subtlety now that under unified architecture a tenant's cluster version may lag behind the system cluster version. We should add a comment to the places where we determine the appropriate table format to use when building an sstable. Maybe there's additional work we should consider.
Jira issue: CRDB-33932
Contributor guide
Assessment
This issue has not been assessed yet.