[CCR][FE Binlog] REPLACE TABLE swap=false checks the old table ID and can lose events
- Dominant language
- Java
- Stars
- 15.9k
- Forks
- 3.9k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 522
Description
## Problem
[CCR][FE Binlog] REPLACE TABLE swap=false checks the old table ID and can lose events
## Minimal reproduction path
Disable database-level CCR Binlog and enable table-level Binlog for two ordinary tables. Execute ALTER TABLE A REPLACE WITH TABLE B PROPERTIES ("swap" = "false") with the old-table cache warm and cold, then compare the metadata Binlog and dropped-table records. Verify that event recording is stable and does not depend on whether the old table remains in a local cache.
## Expected result
swap=false replacement event recording is stable across cache states and does not lose dropped-table metadata.
## Source
This report is a sanitized tracking record for Jira DORIS-28089. Internal hosts, paths, artifacts, build identifiers, and private logs are intentionally omitted.
Contributor guide
Research direction
Start by reproducing ALTER TABLE A REPLACE WITH TABLE B PROPERTIES ("swap" = "false") with database-level CCR Binlog disabled and table-level Binlog enabled. Compare metadata Binlog and dropped-table records with the old-table cache warm and cold; done means replacement event recording is stable and no dropped-table metadata is lost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100