[
https://issues.apache.org/jira/browse/FLINK-30483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651185#comment-17651185
]
Mingliang Liu commented on FLINK-30483:
---------------------------------------
I'm not sure this requires FLINK-17224. Today TIME and TIMESTAMP both support
milliseconds (precision 3). It seems to me only TIME supporting precision
doesn't work correctly and TIMESTAMP just works fine. TIMESTAMP_LTZ in this
JIRA is more related to TIMESTAMP and I guess it's not blocked by FLINK-17224.
FLINK-23589 is to add microseconds (precision 6) support for TIMESTAMP. I think
it is not blocked by FLINK-17224 either. Meanwhile, FLINK-27331 is to add
microseconds precision for TIME which is indeed blocked by FLINK-17224.
I have not looked into those work carefully (or test myself) and could have
missed something.
> Make Avro format support for TIMESTAMP_LTZ
> ------------------------------------------
>
> Key: FLINK-30483
> URL: https://issues.apache.org/jira/browse/FLINK-30483
> Project: Flink
> Issue Type: Improvement
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.16.0
> Reporter: Mingliang Liu
> Priority: Major
>
> Currently Avro format does not support TIMESTAMP_LTZ (short for
> TIMESTAMP_WITH_LOCAL_TIME_ZONE) type. Avro 1.10+ introduces local timestamp
> logic type (both milliseconds and microseconds), see spec [1]. As TIMESTAMP
> currently only supports milliseconds, we can make TIMESTAMP_LTZ support
> milliseconds first.
> A related work is to support microseconds, and there is already
> work-in-progress Jira FLINK-23589 for TIMESTAMP type. We can consolidate the
> effort or track that separately for TIMESTAMP_LTZ.
> [1]
> https://avro.apache.org/docs/1.10.2/spec.html#Local+timestamp+%28millisecond+precision%29
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
