Skip to content

branch-4.1: [fix](streaming-job) propagate ALTER source/target properties to runtime and persistence #62553#62985

Merged
yiguolei merged 1 commit intobranch-4.1from
auto-pick-62553-branch-4.1
May 1, 2026
Merged

branch-4.1: [fix](streaming-job) propagate ALTER source/target properties to runtime and persistence #62553#62985
yiguolei merged 1 commit intobranch-4.1from
auto-pick-62553-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 1, 2026

Cherry-picked from #62553

…ime and persistence (#62553)

### What problem does this PR solve?

ALTER JOB on a non-TVF streaming CDC job could silently fail in two
ways:

1. **Persistence**: `replayOnUpdated` didn't sync `sourceProperties` /
`targetProperties`, so the values were lost after FE checkpoint/restart
or on follower FE.
2. **Runtime**: `JdbcSourceOffsetProvider` held an independent copy of
`sourceProperties` seeded at init time. ALTER on credentials (password,
driver_url, etc.) never reached the provider's BE RPCs — the job would
keep trying the old credentials.

### Fix

1. `replayOnUpdated` now copies `sourceProperties` / `targetProperties`
from the replay job.
2. Job caches a `convertedSourceProperties` (transient) that's refreshed
on ALTER; all provider and task entry points (`fetchMeta` / `cleanup` /
`createStreamingMultiTblTask`) push it to the provider via a new
`ensureInitialized` override.
@github-actions github-actions Bot requested a review from yiguolei as a code owner May 1, 2026 07:48
@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?

@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

@yiguolei yiguolei merged commit 5656c83 into branch-4.1 May 1, 2026
29 of 32 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.

3 participants