viirya commented on issue #1666: URL: https://github.com/apache/arrow-rs/issues/1666#issuecomment-1120282786
Thanks for summarizing the current status and the proposals. @tustvold So looks like we have already used option 2 and option 3 on Timestamp and Date64? I think that we should come out a consistent approach on dealing with this kind of Arrow types. No matter it is option 2 or option 3. > Cast to a native parquet representation, potentially losing precision in the process > Encode the data, only encoding its logical type in the embedded arrow schema I think that above two options are better choices and they have some advantages separately. Regarding with ecosystem compatibility, I feel it might be somehow confused to users too that Parquet files from one arrow implementation is not compatible with other implementations. Especially if the users aren't aware of the fact that the produced Parquet files might be not compatible with other tools. If there is a config/feature used to explicitly enable such unsupported Arrow types in Parquet from this crate. It might be helpful as users will know what they are doing. -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
