[
https://issues.apache.org/jira/browse/FLINK-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181224#comment-16181224
]
ASF GitHub Bot commented on FLINK-7446:
---------------------------------------
Github user fhueske commented on the issue:
https://github.com/apache/flink/pull/4710
Thanks for the review @twalthr.
I've updated the PR.
@haohui: This PR preserves the current logic that time attributes are
exposed as `TIMESTAMP`. I agree that support for time indicators that expose
themselves as `Long` is desirable. However, this requires quite a few changes
as we need to extend several functions (incl. `TUMBLE`, `HOP`, etc.) and
validation logic in some operators (over windows, joins, etc.). So this is not
a lightweight change and should be done as a separate issue, IMO.
> Support to define an existing field as the rowtime field for TableSource
> ------------------------------------------------------------------------
>
> Key: FLINK-7446
> URL: https://issues.apache.org/jira/browse/FLINK-7446
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Jark Wu
> Assignee: Fabian Hueske
>
> Currently {{DefinedRowtimeAttribute}} can define an appended rowtime field
> for a {{TableSource}}. But it would be helpful if we can support to define an
> existing field as the rowtime field. Just like registering a DataStream, the
> rowtime field can be appended but also can replace an existing field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
