chenjian2664 opened a new pull request, #4365:
URL: https://github.com/apache/iceberg-python/pull/4365

   <!--
   Thanks for opening a pull request!
   -->
   
   <!-- In the case this PR will resolve an issue, please replace 
${GITHUB_ISSUE_ID} below with the actual Github issue id. -->
   <!-- Closes #${GITHUB_ISSUE_ID} -->
   
   # Rationale for this change
   
   Within one `update_schema()`, deleting a column, adding it back under the 
same name and then moving it with `move_first`, `move_before` or `move_after` 
raises a bare `StopIteration`. This is a natural way to replace a column with 
an incompatible type while keeping its position. The move resolved the name 
against the existing schema first and picked up the deleted field.
   
   The lookup now checks columns added in the same update first, as Java's 
`SchemaUpdate.findForMove` does.
   
   ## Are these changes tested?
   
   ## Are there any user-facing changes?
   
   <!-- In the case of user-facing changes, please add the changelog 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