You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2018/12/03 12:45:00 UTC

[jira] [Created] (FLINK-11054) Ingest Long value as TIMESTAMP attribute

Fabian Hueske created FLINK-11054:
-------------------------------------

             Summary: Ingest Long value as TIMESTAMP attribute
                 Key: FLINK-11054
                 URL: https://issues.apache.org/jira/browse/FLINK-11054
             Project: Flink
          Issue Type: Improvement
          Components: Table API &amp; SQL
            Reporter: Fabian Hueske


When ingesting streaming tables, a {{Long}} value that is marked as event-time timestamp is automatically converted into a {{TIMESTAMP}} attribute. 
However, batch table scans do not have similar functionality, i.e. to convert a {{Long}} during ingestion / table scan into a {{TIMESTAMP}}. This is relevant because features like GROUP BY windows require a {{TIMESTAMP}} parameter. Hence, batch queries would need to use a UDF (or later built-in function) to manually convert a {{Long}} attribute to {{TIMESTAMP}}.

Flink separates the concepts of format schema and table schema.
I propose to automatically convert values that are defined as {{long}} in the format schema and as {{TIMESTAMP}} in the table schema (both for streaming and batch scans).
Since, the conversion is only done if explicitly requested (right now this should yield an error messages), we should not break existing behavior.

What do you think [~twalthr]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)