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

   ### What problem does this PR solve?
   
   Issue Number: N/A
   
   Related PR: #68248, #69628
   
   Problem Summary:
   When `iceberg.rest.nested-namespace-enabled=true`, Iceberg REST namespace 
discovery recursively lists child namespaces. If another session drops a child 
between listing the parent and listing its children, `NoSuchNamespaceException` 
currently aborts the entire `SHOW DATABASES` result.
   
   This change catches `NoSuchNamespaceException` only at the child recursion 
boundary in the session-aware namespace catalog path. The stale child and its 
descendants are skipped, while failures to list the root and other 
authorization or service failures are still propagated. The behavior matches 
the existing master implementation from #68248 and is adapted to the branch-4.2 
`listNestedNamespaces(activeNsCatalog, parentNs)` signature.
   
   ### Release note
   
   Fix Iceberg REST nested namespace listing when another session drops a 
namespace concurrently.
   
   ### Check List (For Author)
   
   - Test
       - [ ] Regression test
       - [x] Unit Test
       - [ ] Manual test (add detailed scripts or steps below)
       - [ ] No need to test or manual test. Explain why:
           - [ ] This is a refactor/code format and no logic has been changed.
           - [ ] Previous test can cover this change.
           - [ ] No code files have been changed.
           - [ ] Other reason
   
   - Behavior changed:
       - [ ] No.
       - [x] Yes. A concurrently dropped child namespace no longer aborts the 
catalog listing.
   
   - Does this need documentation?
       - [x] No.
       - [ ] Yes.
   
   ### 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