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

   ### What problem does this PR solve?
   
   Issue Number: N/A
   
   Related PR: #69452
   
   Problem Summary:
   
   Backport #69452 to branch-4.1. Iceberg's JDBC catalog implements 
`ViewCatalog` even when its V0 metadata schema does not support views. 
Unsupported view probes must not prevent ordinary table listing or reads.
   
   Adapt the fix to the release branch's legacy `IcebergMetadataOps` 
implementation. Return no views only for unsupported JDBC view probes, 
preserving V1 view support, REST view routing, explicit view-operation 
failures, and real SQL/authorization errors.
   
   Port the six unit-test scenarios to the legacy metadata API and retain the 
original PostgreSQL V0 SELECT-only regression setup and read/time-travel checks.
   
   ### Release note
   
   Fix table discovery and access through Iceberg JDBC catalogs using the V0 
metadata schema without view support.
   
   ### Check List (For Author)
   
   - Test
       - [x] Unit Test: 19 tests passed (six new JDBC probe tests and the 
existing metadata-operation tests), zero failures/errors/skips. FE Checkstyle 
passed. Before the fix, both V0 tests reproduced the actual SDK 
unsupported-view exception.
       - [ ] Regression test: V0 scenarios ported unchanged from #69452; 
release-branch end-to-end execution is left to CI.
   - Behavior changed:
       - [x] Yes. Unsupported JDBC view probes no longer block ordinary table 
operations.
   - Does this need documentation?
       - [x] No.
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label
   


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