Skip to content

branch-4.2: [fix](fe) Propagate JSON properties for multi-table routine load - #69453

Merged
yiguolei merged 1 commit into
apache:branch-4.2from
sollhui:pick-67510-branch-4.2
Oct 23, 2026
Merged

yiguolei merged 1 commit into
apache:branch-4.2from
sollhui:pick-67510-branch-4.2

Conversation

@sollhui

@sollhui sollhui commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

What problem does this PR solve?

Issue Number: None

Related PR: #67510

Problem Summary: Backport #67510 to branch-4.2. Multi-table routine load rebuilds stream-load tasks when planning dynamic target tables, but omitted the job's jsonpaths and num_as_string properties. Propagate both properties so per-table plans honor the configured JSON paths and number handling.

The target branch does not contain NereidsStreamLoadTaskTest, so this backport adds the JSON-property test as a new file.

Release note

Fix multi-table routine load to honor jsonpaths and num_as_string for dynamic target tables.

Check List (For Author)

  • Test: Compilation and tests skipped as requested. The original PR's unit test is included in this backport. CI requested with run buildall.
  • Behavior changed: Yes. Multi-table routine load applies configured jsonpaths and num_as_string during per-table planning.
  • Does this need documentation: No.

@sollhui
sollhui requested a review from yiguolei as a code owner October 22, 2026 08:33
@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?

@sollhui

sollhui commented Oct 22, 2026

Copy link
Copy Markdown
Contributor Author

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 100.00% (2/2) 🎉
Increment coverage report
Complete coverage report

@hello-stephen

Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 100.00% (2/2) 🎉
Increment coverage report
Complete coverage report

@yiguolei
yiguolei merged commit 747fff3 into apache:branch-4.2 Oct 23, 2026
29 of 30 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

PR approved by anyone and no changes requested.

@github-actions github-actions Bot added the approved Indicates a PR has been approved by one committer. label Oct 23, 2026
@github-actions

Copy link
Copy Markdown
Contributor

PR approved by at least one committer and no changes requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants