[Python][C++] Impossible to specify `is_adjusted_to_utc` for Time type when writing to Parquet

[LoganDark]

Describe the enhancement requested

TL;DR this code

arrow/cpp/src/parquet/arrow/schema.cc

Line 396 in 0ef7351

LogicalType::Time(/*is_adjusted_to_utc=*/true, LogicalType::TimeUnit::MICROS);

hardcodes is_adjusted_to_utc=true, which makes it impossible to change from pyarrow.parquet.write_table.

It should probably be an optional parameter that is passed down similar to coerce_timestamps

Component(s)

C++, Python

[jorisvandenbossche]

@LoganDark thanks for the report. I can see why you might want to specify this, since there is no other way to control it (in contrast to Timestamp type, where it is controlled by having a timezone attached to the arrow type or not)

In hindsight, I am also thinking that it would actually be more correct for Arrow to use is_adjusted_to_utc=false by default. But I assume true was used to follow the backward/forward compatibility guidelines (https://github.com/apache/parquet-format/blob/master/LogicalTypes.md#deprecated-time-convertedtype)

[LoganDark]

In hindsight, I am also thinking that it would actually be more correct for Arrow to use is_adjusted_to_utc=false by default.

I agree

I assume true was used to follow the backward/forward compatibility guidelines

Probably, that's also the reference I used to discover the existence/behavior of this option. It doesn't say this has to be the same as the legacy ConvertedType, though, just that the ConvertedType should be converted forward a particular way (with isAdjustedToUTC = true). So that shouldn't preclude adding a new option, though changing the default may be a breaking change.

[kangakum36]

Can I take this issue?

[LoganDark]

Of course.