[
https://issues.apache.org/jira/browse/FLINK-17868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258680#comment-17258680
]
Jark Wu commented on FLINK-17868:
---------------------------------
Hi [~qingyue], I'm perfer the Alternative#1, because we should keep the
semantic/behavior consistent between streaming and batch.
{{CURRENT_TIMESTAMP()}} is not a synonyms for {{PROCTIME()}}.
Regarding to the implementation, I think we can try to merge
{{AbstractProcessStreamOperator}} into {{TableStreamOperator}}, then streaming
and batch operators can share the same base class.
I assigned this issue to you.
> Proctime in DDL can not work in batch mode
> ------------------------------------------
>
> Key: FLINK-17868
> URL: https://issues.apache.org/jira/browse/FLINK-17868
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: Jingsong Lee
> Priority: Major
> Labels: sprint
> Fix For: 1.13.0
>
>
> The data of this proctime column will be all null. Should same to current
> timestamp.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)