[
https://issues.apache.org/jira/browse/FLINK-15528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
godfrey he updated FLINK-15528:
-------------------------------
Component/s: (was: Table SQL / Planner)
Table SQL / API
> 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: Sub-task
> Components: Table SQL / API
> Reporter: Jark Wu
> Priority: Major
>
> 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)
