dannycjones commented on issue #3258: URL: https://github.com/apache/iceberg-rust/issues/3258#issuecomment-5774963118
I'm still building a better understanding around the read and write pipelines. I think what's concerning to me is that its unclear right now if we merge in say the types to model geospatial or unknown, etc. what behavior will be ungated. When the code is merged in, that could be a version that we ultimately cut a release from and may allow consumers to start read/writing this data which could be read and written incorrectly. Ultimately, we shouldn't be allowing them to be merged without the proper gates in place. We do ensure that, for example variant is blocking on read by rejecting it when building the projection mask on write when constructing the Parquet path visitor. I'm reaching for something more standardized and obvious (although maybe these points are already the more obvious places when more familiar with the code). -- 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]
