Skip to content

[Feature](routine_load) auto fill missing columns#64071

Open
billryan wants to merge 1 commit into
apache:masterfrom
billryan:feature/auto-fill-missing-columns
Open

[Feature](routine_load) auto fill missing columns#64071
billryan wants to merge 1 commit into
apache:masterfrom
billryan:feature/auto-fill-missing-columns

Conversation

@billryan
Copy link
Copy Markdown

@billryan billryan commented Jun 3, 2026

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

For routine load jobs, if we have thousands of columns to import, we can use json format let doris automatically match the column name with table schema. But for some scenarios, the upstream data does not have the column name(can be derived from current columns) and we can not add new column name easily, so we consider if we can just specify the new derived column only and let doris fill the missing columns with table schema.

e.g.

The MQ data have stat_time_day field but does not have p_date column, we can add new column like this p_date = stat_time_day, fill missing columns from table schema.

CREATE ROUTINE LOAD db.job_name ON table_a
COLUMNS(p_date = stat_time_day)
PROPERTIES (
    "format" = "json",
    "fill_missing_columns" = "true"
)
FROM KAFKA (...);

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@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?

@billryan billryan force-pushed the feature/auto-fill-missing-columns branch from 531f6aa to 43168c2 Compare June 4, 2026 03:55
@billryan
Copy link
Copy Markdown
Author

billryan commented Jun 4, 2026

/review

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.

2 participants