[CCR][FE Binlog] Temporary-table CREATE is filtered but DROP_TABLE still enters the database Binlog
- Dominant language
- Java
- Stars
- 15.9k
- Forks
- 3.9k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 520
Description
## Problem
[CCR][FE Binlog] Temporary-table CREATE is filtered but DROP_TABLE still enters the database Binlog
## Minimal reproduction path
Enable database-level CCR metadata Binlog, create a temporary OLAP table, and immediately drop it. Inspect the database Binlog and dropped-table records. Verify that the temporary table produces neither CREATE_TABLE nor DROP_TABLE metadata events, while an ordinary table still produces the expected drop event.
## Expected result
Temporary-table CREATE and DROP are consistently excluded from database metadata Binlog.
## Source
This report is a sanitized tracking record for Jira DORIS-28092. Internal hosts, paths, artifacts, build identifiers, and private logs are intentionally omitted.
Contributor guide
Research direction
Start by enabling database-level CCR metadata Binlog and reproducing the temporary-table CREATE and DROP sequence described in the issue. Inspect the resulting database Binlog and dropped-table records; done means temporary tables produce neither CREATE_TABLE nor DROP_TABLE events while ordinary tables still produce the expected drop event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100