Skip to content

[fix](regression) Stabilize external table guardrail cases - #66509

Open
Gabriel39 wants to merge 1 commit into
apache:branch-4.1from
Gabriel39:fix/external-case-guardrails-4.1
Open

[fix](regression) Stabilize external table guardrail cases#66509
Gabriel39 wants to merge 1 commit into
apache:branch-4.1from
Gabriel39:fix/external-case-guardrails-4.1

Conversation

@Gabriel39

Copy link
Copy Markdown
Contributor

What problem does this PR solve?

The external-table regression suite had two environment-dependent failures:

  • The Paimon guardrail case attempted to create a table with an empty field name. Paimon rejects empty and whitespace-only field names while constructing the table schema, before Doris can scan it.
  • The Iceberg Variant case required more than one scanner to report rows. File scanner tasks pull ranges dynamically, so minimum scanner concurrency does not guarantee that every scheduled scanner consumes rows from a small multi-file fixture.

What is changed?

  • Remove the unsupported empty-field Paimon fixture and its expected results. Delimiter-rich field names remain covered end to end, while empty-segment framing remains covered by the codec unit test.
  • Keep the parallel Iceberg Variant correctness query, but remove the assertion on nondeterministic per-scanner range assignment.

Validation

  • test_paimon_jni_reader_guardrails: passed
  • test_iceberg_variant_read: passed twice consecutively

Release note

None. These are test-only corrections.

@Gabriel39
Gabriel39 requested a review from yiguolei as a code owner August 5, 2026 15:58
@Gabriel39

Copy link
Copy Markdown
Contributor Author

run buildall

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

@Gabriel39

Copy link
Copy Markdown
Contributor Author

/review

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Codex automated review failed and did not complete.

Error: All Codex review accounts are usage-limited; earliest retry is 2026-08-08T03:32:00Z.
Workflow run: https://github.com/apache/doris/actions/runs/31023047435

Please trigger /review again after that time.

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