[
https://issues.apache.org/jira/browse/FLINK-34536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823143#comment-17823143
]
yisha zhou commented on FLINK-34536:
------------------------------------
[~libenchao] Thanks for your insight, it helps a lot! After reading FLIP-162, I
think explicit calling of `to_timestamp_ltz` maybe more reasonable and
conforming to design. Otherwise we should expose configs for users to declare
the details about the conversion, e.g. precision. It seems to be too complex.
> Support reading long value as Timestamp column in JSON format
> -------------------------------------------------------------
>
> Key: FLINK-34536
> URL: https://issues.apache.org/jira/browse/FLINK-34536
> Project: Flink
> Issue Type: Improvement
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.19.0
> Reporter: yisha zhou
> Priority: Major
>
> In many scenarios, timestamp data is stored as Long value and expected to be
> operated as Timestamp value. It's not user-friendly to use an UDF to convert
> the data before operating it.
> Meanwhile, in Avro format, it seems it can receive several types of input and
> convert it into TimestampData. Hope the same ability can be introduced into
> JSON format.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
