You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/10/27 10:38:00 UTC
[jira] [Comment Edited] (FLINK-17525) Support to parse millisecond
and nanoseconds for TIME type in CSV and JSON format
[ https://issues.apache.org/jira/browse/FLINK-17525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221307#comment-17221307 ]
Jark Wu edited comment on FLINK-17525 at 10/27/20, 10:37 AM:
-------------------------------------------------------------
Sure. But if I remember correctly, the planner doesn't support nanoseconds for TIME type yet. But millisecond is supported. You can support millisecond for CSV first.
was (Author: jark):
Sure. But if I remember correctly, the planner doesn't support nanoseconds for TIME type yet.
> 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: Major
>
> 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.3.4#803005)