[
https://issues.apache.org/jira/browse/FLINK-15560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321424#comment-17321424
]
Flink Jira Bot commented on FLINK-15560:
----------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> Timestamp literal support for startFromTimestamp in KafkaTableSource
> --------------------------------------------------------------------
>
> Key: FLINK-15560
> URL: https://issues.apache.org/jira/browse/FLINK-15560
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Ecosystem
> Reporter: Paul Lin
> Priority: Minor
> Labels: stale-minor
>
> The follow-up work for FLINK-15220 which leaves timestamp literal support
> unimplemented, because the time zone is not available for the user-specified
> timestamps in form of `yyyy-MM-dd HH:mm:ss[.SSS]`, as `TableConfig` is not
> yet exposed to `TableFactory`.
> Explicitly setting time zones in the timestamp literals may be an option, but
> it is a bit troublesome and may result in inconsistency if we get different
> time zones in timestamp literals and `TableConfig`.
> h3. API changes
> Add the following config to DDL api:
>
> ```
> 'connector.startup-timestamp' = '2019-12-12 10:11:23.123'
> ```
>
> The timestamp would need to be in form of milliseconds from epoch or
> "yyyy-MM-dd HH:mm:ss[.SSS]". If both `connector.startup-timestamp` and
> `connector.startup-timestamp-millis` are provided, a validation exception
> would be thrown.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
