[
https://issues.apache.org/jira/browse/FLINK-22275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413950#comment-17413950
]
Jark Wu commented on FLINK-22275:
---------------------------------
[~yittg] thanks for the updating. I will review it later.
> Datagen add a max lag option for a series of timestamp-related types
> --------------------------------------------------------------------
>
> Key: FLINK-22275
> URL: https://issues.apache.org/jira/browse/FLINK-22275
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Ecosystem
> Reporter: Yi Tang
> Assignee: Yi Tang
> Priority: Minor
> Labels: pull-request-available, stale-assigned
> Fix For: 1.14.0
>
>
> For now, the {{datagen}} connector always resolves to the current timestamp
> for timestamp-related types.
> Here proposals to add a max lag option for these types, which will generate a
> timestamp with a random lag (with max lag as option) compared with the
> current timestamp. Leave it as before if the option is not configured.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
