Skip to content

branch-4.2: [fix](fe) Skip table snapshot resolution for external views (#69836) - #70292

Draft
hubgeter wants to merge 1 commit into
apache:branch-4.2from
hubgeter:pick/69836-branch-4.2
Draft

hubgeter wants to merge 1 commit into
apache:branch-4.2from
hubgeter:pick/69836-branch-4.2

Conversation

@hubgeter

@hubgeter hubgeter commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

pick #69836

### What problem does this PR solve?

Issue Number: N/A

Related PR: apache#69836

Problem Summary: Statement snapshot binding runs before external view SQL expansion. branch-4.2 already returns EmptyMvccSnapshot for Iceberg views, but silently ignores relation scan parameters and then reads the default view SQL. Reject every TableScanParams value before returning the existing empty view snapshot. Preserve the legacy Iceberg table path and the inherited MVCC overloads. Add tests for ordinary views and branch/tag list and map selectors, incremental reads, and options without table metadata access.

### Release note

Reject unsupported branch, tag, incremental, and options scan parameters on Iceberg views instead of silently ignoring them.

### Check List (For Author)

- Test: Unit Test / FE build and Checkstyle
    - run-fe-ut.sh --run org.apache.doris.datasource.iceberg.IcebergExternalTableTest: 25 passed, 0 failures, 0 errors, 0 skipped; reused main classes freshly compiled in this worktree.
    - build.sh --fe with UI disabled: the complete 27-module Maven reactor compiled and passed Checkstyle. After a verified Lance JNI download, the final FE packaging run reused the compiled classes and completed successfully with unrelated extension packaging disabled.
    - git diff --check passed. External catalog end-to-end regression was not run.
- Behavior changed: Yes; unsupported view scan parameters now fail explicitly.
- Does this need documentation: No
@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?

@hubgeter

hubgeter commented Nov 5, 2026

Copy link
Copy Markdown
Contributor Author

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 0.00% (0/3) 🎉
Increment coverage report
Complete coverage report

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