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

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: None
   
   Problem Summary: Dropping an Iceberg column can leave historical partition 
specs referencing a field ID that no longer exists in the current schema, which 
makes historical metadata unreadable. The same failure occurs when dropping a 
struct ancestor of a referenced nested field. Resolve top-level and nested drop 
targets before committing the schema update, then reject the drop when any 
historical partition spec references the target field or a field in its subtree.
   
   ### Release note
   
   Iceberg column drops now fail explicitly when the column, or a nested field 
beneath it, is referenced by a historical partition spec.
   
   ### 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. Invalid Iceberg column drops are rejected before corrupting 
historical partition metadata.
   
   - 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