dannycjones opened a new issue, #3258: URL: https://github.com/apache/iceberg-rust/issues/3258
### Is your feature request related to a problem or challenge? As we implement the V3 data types, a lot of hazards are found as we have to carefully understand each part of the read or write path to ensure we don't silently write corrupt data. For example, geospatial types support a different kind of bounds than other primitive types but the bytes would be used verbatim without introducing a specific check. ### Describe the solution you'd like I'd like to propose gates on the read/write path based on how much is implemented in iceberg-rust. For example, we can implement variant type handling in table metadata (as we have done already) and block both read and write path until we've fully tested each one. The proposal would be to gate the read and write path independently. Additionally, gating them doesn't mean that they're _fully_ implemented, just that they can be safely read and written. For example, we could allowlist geospatial writes even if we omit data file bounds in the manifest entries - as they are optional in the spec. ### Willingness to contribute I can contribute to this feature independently -- 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]
