hubgeter opened a new pull request, #70370:
URL: https://github.com/apache/doris/pull/70370

   ### Background
   
   Iceberg stores a view's SQL, output schema and default namespace separately.
   
   ### What problem does this PR solve?
   
   Issue Number: None
   Related PR: #69836
   PR Type: Bugfix
   
   Problem Summary:
   
   Views can resolve base tables in the wrong namespace and expose expression 
names instead of their declared column names. Capture one view definition per 
statement and bind its saved defaults and independent output aliases.
   
   ### Details
   
   - **Change map:** 157 production lines, 373 test lines and 8 API baseline 
lines.
   - **Frequency:** views with renamed/repeated columns or a source namespace 
different from the view location.
   - **Root cause:** SQL, schema and resolution defaults were bound 
independently.
   - **Why existing tests missed it:** missing coverage for declared repeated 
columns and separate source/view namespaces.
   - **Fix:** capture a consistent view version and carry saved defaults 
through Connector SPI (API 31.0).
   - **Other paths and branches:** connectors without saved defaults keep their 
existing owning-database fallback.
   
   ### Testing
   
   - Local FE build, including Checkstyle: passed.
   - 287 unit tests across 42 classes: passed.
   - Full REST regression is in progress; a matching local ASAN BE is being 
built.
   
   ### Release note
   
   Iceberg view queries honor saved namespaces and declared output column names.
   
   ### Check List (For Author)
   
   - Behavior changed: Yes (view name and namespace binding).
   - Does this need documentation: No.
   - Pre-submission status: Partially verified; full integration tests and CI 
pending.
   
   ### AI Disclosure
   
   - Tool: Codex.
   - Generated: code, tests and description.
   - Human review: Pending (draft).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to