Skip to content

branch-4.1: [Improve](streaming-job) support specifying offset for StreamingInsertJob create and alter #62490#62853

Open
github-actions[bot] wants to merge 1 commit intobranch-4.1from
auto-pick-62490-branch-4.1
Open

branch-4.1: [Improve](streaming-job) support specifying offset for StreamingInsertJob create and alter #62490#62853
github-actions[bot] wants to merge 1 commit intobranch-4.1from
auto-pick-62490-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Cherry-picked from #62490

…tJob create and alter (#62490)

## Summary
- Support specifying offset (binlog position, LSN, named modes) when
creating or altering a StreamingInsertJob via `FROM MYSQL/POSTGRES`
path.
- FE: extend `DataSourceConfigValidator` to validate offset formats
(initial/snapshot/latest/earliest/JSON); `earliest` is MySQL-only,
rejected for PostgreSQL. Implement
`JdbcSourceOffsetProvider.deserializeOffsetProperty()` for named modes
and JSON offset parsing. Remove S3-only restriction in
`StreamingInsertJob.initInsertJob()` and `modifyPropertiesInternal()` so
CDC jobs can also use offset property. On ALTER, sync offset to
`sourceProperties` for the FROM...TO path.
- BE: support JSON LSN offset `{"lsn":"N"}` in
`PostgresSourceReader.generatePostgresConfig()`, and handle
`SPECIFIC_OFFSETS` mode in
`JdbcIncrementalSourceReader.getStartOffsetFromConfig()`.
- Fix `JdbcOffset.isValidOffset()` and `toSerializedJson()` to return
meaningful values instead of hardcoded false/null.
@github-actions github-actions Bot requested a review from yiguolei as a code owner April 27, 2026 03:54
@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 Apr 27, 2026
@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

@JNSimba
Copy link
Copy Markdown
Member

JNSimba commented Apr 27, 2026

run p0

@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 14.52% (9/62) 🎉
Increment coverage report
Complete coverage report

1 similar comment
@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 14.52% (9/62) 🎉
Increment coverage report
Complete coverage report

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