[fix](fe) Propagate JSON properties for multi-table routine load - #67510
Open
0AyanamiRei wants to merge 1 commit into
Open
[fix](fe) Propagate JSON properties for multi-table routine load#675100AyanamiRei wants to merge 1 commit into
0AyanamiRei wants to merge 1 commit into
Conversation
### What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: Multi-table routine load defers planning until the backend discovers each target table. The follow-up FE planning task restored json_root and strip_outer_array from the routine load job but omitted jsonpaths and num_as_string, so nested JSON records were planned without their configured paths and were filtered as invalid rows. Copy these properties into the per-table stream load task so the generated scan parameters match the routine load definition.
### Release note
Fix multi-table routine load to honor jsonpaths and num_as_string for dynamic target tables.
### Check List (For Author)
- Test: Unit Test and FE build
- sh run-fe-ut.sh --run org.apache.doris.nereids.load.NereidsStreamLoadTaskTest
- DISABLE_BUILD_UI=ON ./build.sh --fe -j48
- Behavior changed: Yes. Multi-table routine load now applies configured jsonpaths and num_as_string during per-table planning.
- Does this need documentation: No
0AyanamiRei
requested review from
924060929,
englefly,
morrySnow and
starocean999
as code owners
September 3, 2026 17:27
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: Multi-table routine load cannot attach a table-specific pipeline plan before the backend discovers the destination table. The backend therefore requests a per-table plan with the format, and FE rebuilds the stream-load task from the Routine Load job. That rebuild already restored
json_rootandstrip_outer_array, but omittedjsonpathsandnum_as_string. Nested JSON records were consequently planned with an empty JSON path list and filtered as invalid rows. This change restores those two properties before generating each dynamic-table pipeline plan.Release note
Fix multi-table routine load to honor
jsonpathsandnum_as_stringfor dynamic target tables.Check List (For Author)
Test
sh run-fe-ut.sh --run org.apache.doris.nereids.load.NereidsStreamLoadTaskTestDISABLE_BUILD_UI=ON ./build.sh --fe -j48Behavior changed:
jsonpathsandnum_as_stringduring per-table planning.Does this need documentation?
Check List (For Reviewer who merge this PR)