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/01/09 04:15:00 UTC
[jira] [Created] (FLINK-15528) Support higher precision of
TIMESTAMP type as rowtime attribute
Jark Wu created FLINK-15528:
-------------------------------
Summary: Support higher precision of TIMESTAMP type as rowtime attribute
Key: FLINK-15528
URL: https://issues.apache.org/jira/browse/FLINK-15528
Project: Flink
Issue Type: New Feature
Components: Table SQL / Planner
Reporter: Jark Wu
Currently, we only support TIMESTAMP(3) as rowtime attribute. But Blink planner already opened the door for TIMESTAMP(9). And many built-in functions will return TIMESTAMP(9), e.g. {{TO_TIMESTAMP(VARCHAR)}}, see FLINK-14925.
If a user use TO_TIMESTAMP(log) to parser a string to timestamp and want use it as rowtime attribute, it will fail because the 9 precision. I would be more convenient for users if we can support TIMESTAMP(9) as rowtime attribute.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)