David-Banquet commented on issue #3977: URL: https://github.com/apache/iceberg-python/issues/3977#issuecomment-5995446872
The Java Glue catalog might help with the design question. `GlueTableOperations.prepareProperties` starts from the `Parameters` already in Glue and only sets `table_type`, `metadata_location` and `previous_metadata_location` ([GlueTableOperations.java#L291-L300](https://github.com/apache/iceberg/blob/94250b2527f9e24082134be7da247ff5fc55df8c/aws/src/main/java/org/apache/iceberg/aws/glue/GlueTableOperations.java#L291-L300)). It never copies the Iceberg table properties into `Parameters`: `setTableInputInformation` reads them only for the description and the additional locations ([IcebergToGlueConverter.java#L245-L264](https://github.com/apache/iceberg/blob/94250b2527f9e24082134be7da247ff5fc55df8c/aws/src/main/java/org/apache/iceberg/aws/glue/IcebergToGlueConverter.java#L245-L264)). So Java keeps every key it didn't write, like the Athena and crawler keys in @ArulJerald's table, and it has no drift because it doesn't mirror table properties at all. Of the two options, the surgical prune keeps that guarantee. A full rebuild would make PyIceberg drop keys that Java leaves alone on the same table. -- 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]
