[
https://issues.apache.org/jira/browse/FLINK-17525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731464#comment-17731464
]
Sergey Nuyanzin commented on FLINK-17525:
-----------------------------------------
Also it looks it is related to FLINK-17224
> Support to parse millisecond and nanoseconds for TIME type in CSV and JSON
> format
> ---------------------------------------------------------------------------------
>
> Key: FLINK-17525
> URL: https://issues.apache.org/jira/browse/FLINK-17525
> Project: Flink
> Issue Type: New Feature
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile), Table
> SQL / Ecosystem
> Reporter: Jark Wu
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> Currently, CSV and JSON format parse time string but ignores the millisecond
> and nanoseconds part. We should support that, because blink planner already
> support higher precision for TIME.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
