flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Hueske (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8094) Support other types for ExistingField rowtime extractor
Date Thu, 16 Nov 2017 15:59:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-8094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255516#comment-16255516

Fabian Hueske commented on FLINK-8094:

+1 for having a rowtime extractor for string fields. 
As a first approach, we can use a String to Timestamp Cast expression that expects a timestamp
in standard formatting.
Later we can add dedicated parse expressions for timestamp and date to the Table API expressions.
That way we don't need a UDF.

I'd add support for UDFs in extractors as a separate step.

> Support other types for ExistingField rowtime extractor
> -------------------------------------------------------
>                 Key: FLINK-8094
>                 URL: https://issues.apache.org/jira/browse/FLINK-8094
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>    Affects Versions: 1.4.0, 1.5.0
>            Reporter: Xingcan Cui
> Currently, the {{ExistingField}} rowtime extractor only supports {{Long}} and {{Timestamp}}
fields. To enable other data types (e.g., {{String}}), we can provide some system extraction
functions and allow users to pass some parameters via the constructor of {{ExistingField}}.
There's [a simple demo|https://github.com/xccui/flink/commit/afcc5f1a0ad92db08294199e61be5df72c1514f8]
which enables the {{String}} type rowtime by adding a UDF {{str2EventTime}}.

This message was sent by Atlassian JIRA

View raw message