-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kvserver: support MVCC range tombstones in Export #71398
Copy link
Copy link
Closed
Labels
A-kv-replicationRelating to Raft, consensus, and coordination.Relating to Raft, consensus, and coordination.A-kv-serverRelating to the KV-level RPC serverRelating to the KV-level RPC serverC-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)
Metadata
Metadata
Assignees
Labels
A-kv-replicationRelating to Raft, consensus, and coordination.Relating to Raft, consensus, and coordination.A-kv-serverRelating to the KV-level RPC serverRelating to the KV-level RPC serverC-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)
In #70412, we are implementing MVCC range tombstones. These must be integrated with
Export. It is still unclear whether we should export range tombstones as a separate type, or synthesize point deletion tombstones instead, for revision ALL exports (with extended testing). This question also applies for CDC changefeeds in #70433, so maybe discuss with that team first.Epic CRDB-2624
Jira issue: CRDB-10553