You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2019/03/22 09:43:00 UTC

[jira] [Updated] (FLINK-9864) Make timestamp extraction more flexible in SQL Client

     [ https://issues.apache.org/jira/browse/FLINK-9864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aljoscha Krettek updated FLINK-9864:
------------------------------------
    Component/s:     (was: Table SQL / API)

> Make timestamp extraction more flexible in SQL Client
> -----------------------------------------------------
>
>                 Key: FLINK-9864
>                 URL: https://issues.apache.org/jira/browse/FLINK-9864
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / Client
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>
> Currently, a timestamp must be in the top-level of a possibly nested row and must have a certain format. We should think about making this more flexible to cover most of the use cases.
> A first solution could be to allow a DOT operator syntax: {{myfield.nested.timestamp}}
> Other cases might be:
> - The time could also be split into several field
> - Or needs to be parsed using a [date format syntax|https://ci.apache.org/projects/flink/flink-docs-master/dev/table/sql.html#date-format-specifier].



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