You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/01/02 10:40:00 UTC
[jira] [Updated] (FLINK-21716) Support higher precision for Data Type TIME(p)
[ https://issues.apache.org/jira/browse/FLINK-21716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-21716:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned (was: auto-deprioritized-major auto-unassigned stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.
> Support higher precision for Data Type TIME(p)
> -----------------------------------------------
>
> Key: FLINK-21716
> URL: https://issues.apache.org/jira/browse/FLINK-21716
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Leonard Xu
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned
>
> Due to the historical reason, we only support TIME(3) yet, we can support higher precision eg. TIME(9).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)