yihua opened a new issue, #812: URL: https://github.com/apache/hudi-rs/issues/812
## Problem `avro_to_arrow::schema` still has `todo!()` arms for the Avro logical types `local-timestamp-millis`, `local-timestamp-micros` and `local-timestamp-nanos`. Any table whose Avro schema declares such a column cannot have its schema converted: the conversion panics as soon as the column is reached, whether or not the query selects it. This is not an unsupported-feature error the caller can handle. It is a panic, and when the conversion runs behind an FFI boundary (the C++ and Python bindings) the panic aborts the host process. Related: #636, which asks for `catch_unwind` at the FFI entry points; this issue is one of the panics that would be caught there, but it should not panic in the first place. ## Expected The three logical types map to a timezone-less Arrow `Timestamp` of the matching unit. That is the type `arrow-avro` decodes the values to, and the type a parquet base file written with `isAdjustedToUTC=false` reads back as, so the Avro-derived table schema and the file schemas agree. -- 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]
