Skip to content

branch-4.1: [Feature](tvf) Support cdc stream tvf for mysql and pg #60116#61840

Merged
yiguolei merged 1 commit intobranch-4.1from
auto-pick-60116-branch-4.1
Mar 30, 2026
Merged

branch-4.1: [Feature](tvf) Support cdc stream tvf for mysql and pg #60116#61840
yiguolei merged 1 commit intobranch-4.1from
auto-pick-60116-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Cherry-picked from #60116

### What problem does this PR solve?

#58898 #59461 These two features support consuming data from MySQL and
PostgreSQL.

Based on this, this PR introduces cdc_stream tvf, which allows consuming
data from MySQL and PostgreSQL in TVF format.

Example
```
select * from cdc_stream(
    "type" = "mysql",
    "jdbc_url" = "jdbc:mysql://127.0.0.1:3306",
    "driver_url" = "mysql-connector-j-8.0.31.jar",
    "driver_class" = "com.mysql.cj.jdbc.Driver",
    "user" = "root",
    "password" = "123456",
    "database" = "test_cdc_db",
    "table" = "user_info",
    "offset" = '{"file":"binlog.000003","pos":"496"}'
)
```
@github-actions github-actions bot requested a review from yiguolei as a code owner March 28, 2026 03:02
@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this Mar 28, 2026
@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 2.90% (2/69) 🎉
Increment coverage report
Complete coverage report

@doris-robot
Copy link
Copy Markdown

BE UT Coverage Report

Increment line coverage 0.00% (0/82) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.93% (19638/37104)
Line Coverage 36.25% (183629/506561)
Region Coverage 32.57% (142079/436197)
Branch Coverage 33.79% (62478/184918)

@JNSimba
Copy link
Copy Markdown
Member

JNSimba commented Mar 28, 2026

run p0

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 71.95% (59/82) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 72.87% (26468/36320)
Line Coverage 56.20% (283753/504866)
Region Coverage 53.81% (236855/440167)
Branch Coverage 55.52% (102957/185446)

@yiguolei yiguolei merged commit 7dd40bd into branch-4.1 Mar 30, 2026
25 of 29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants