paleolimbot commented on PR #526: URL: https://github.com/apache/parquet-format/pull/526#issuecomment-3377638416
> BTW, do you want to port the wraparound logic from arrow-rs to arrow-cpp? Yes! I had hoped for Arrow 22 but given the feature freeze tomorrow I think that's unlikely (I can definitely ensure this and the null count are updated for Arrow 23). > It seems that the two proposals may add additional attributes to the geospatial logical types. I don't think either of those options intends to make changes to the Parquet geometry type that would break the assumptions of existing readers (I suppose the second one adds an option to the geography enum, which would require readers to update their enums). From the Parquet end of things the first option is just a way to signal to Parquet via writer options that `wraparound_hint` should be set. In any case, I don't think these are planning to assign alternative meaning to `xmin` and `xmax` that would make it necessary to force existing implementations to reject `xmax > xmin`? -- 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]
