Re: [I] SchemaUpdate cannot move a column by its new name after renameColumn in the same update [iceberg]

["yusufyildiz34 (via GitHub)" <gi...@apache.org>]

yusufyildiz34 commented on issue #16581:
URL: https://github.com/apache/iceberg/issues/16581#issuecomment-6372270363

   I'd like to pick this up. It's the same problem as #10830, where @RussellSpitzer and @Fokko agreed it isn't intended, and #12202 tried to fix it before the stale bot closed it. My plan is for `SchemaUpdate` to also resolve a column's pending new name in the update and move methods (`updateColumn`, `updateColumnDoc`, `requireColumn`, `makeColumnOptional`, `updateColumnDefault`, `moveFirst`, `moveBefore`, `moveAfter`), only when the name doesn't match an existing or added column, so original names keep working as they do today.
   


-- 
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: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org