[
https://issues.apache.org/jira/browse/FLINK-17525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17525:
-----------------------------------
Labels: auto-deprioritized-major auto-unassigned (was: auto-unassigned
stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> 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: Minor
> Labels: auto-deprioritized-major, 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.3.4#803005)
