You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Paul Lin (Jira)" <ji...@apache.org> on 2020/01/12 14:36:00 UTC
[jira] [Updated] (FLINK-15560) Timestamp literal support for
startFromTimestamp in KafkaTableSource
[ https://issues.apache.org/jira/browse/FLINK-15560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lin updated FLINK-15560:
-----------------------------
Description:
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`.
# 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.
was:
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`.
## 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.
> Timestamp literal support for startFromTimestamp in KafkaTableSource
> --------------------------------------------------------------------
>
> Key: FLINK-15560
> URL: https://issues.apache.org/jira/browse/FLINK-15560
> Project: Flink
> Issue Type: Improvement
> Reporter: Paul Lin
> Priority: 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`.
>
> # 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)