bknbkn opened a new pull request, #11387:
URL: https://github.com/apache/iceberg/pull/11387

   fix #11314  
   
   In the previous code, each spec reads the latest schema. After deleting the 
corresponding field, the historical spec cannot find the corresponding field in 
the current schema, and an error will occur.
   
   This patch **persist the schema id corresponding to the spec. The historical 
spec can read the corresponding schema, and the current spec will be updated to 
the current schema**
   
   But even if the partition field is deleted in the V1 table, it will not be 
deleted in the spec. Therefore, the latest spec is not compatible with the 
schema after the field is deleted. So I prefer to forbid  the V1 table from 
deleting the existing partition field (by Partition#checkCompatibility method 
guarantee)
   
   For V2 tables, it is safe to delete the corresponding column after deleting 
the partition field


-- 
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-unsubscr...@iceberg.apache.org

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


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

Reply via email to