Skip to content

branch-4.2: [fix](fe) Preserve inferred JSON column name casing - #69451

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

yiguolei merged 1 commit into
apache:branch-4.2from
sollhui:pick-67411-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: #67411

Problem Summary: Backport #67411 to branch-4.2. JSON schema inference lowercased field names while JSON readers match object keys case-sensitively, causing mixed-case and uppercase keys to return NULL. Preserve inferred JSON key casing, retain case-insensitive duplicate detection, and keep existing lowercase behavior for other file formats.

The conflict resolution also preserves branch-4.2's existing Lance column name casing behavior.

Release note

JSON table-valued functions now read inferred mixed-case and uppercase keys without silently producing NULL values.

Check List (For Author)

  • Test: Compilation and tests skipped as requested. The original PR's regression test and fixture are included in this backport. CI requested with run buildall.
  • Behavior changed: Yes. Inferred JSON field names preserve source casing.
  • Does this need documentation: No.

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

Increment line coverage 87.50% (7/8) 🎉
Increment coverage report
Complete coverage report

@yiguolei

Copy link
Copy Markdown
Contributor

skip buildall

@yiguolei
yiguolei merged commit 56043de into apache:branch-4.2 Oct 23, 2026
31 of 32 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