RussellSpitzer commented on issue #4849:
URL: https://github.com/apache/iceberg/issues/4849#issuecomment-1146868271

   @kbendick I do think we should allow this, just ignoring the schema change. 
Currently the behavior of merge schema invalidates a write that would succeed 
if mergeSchema had been set to false.
   
   I think in cases like this merge schema should just not downcast and allow 
the write to proceed as normal. This would be really useful for users who have 
multiple numeric sources and want to use mergeSchema functionality. Mostly the 
merge schema is being used for adding new missing columns but if an existing 
column has a wider type (or was widened by another operation) I don't think 
that should break anything


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