[
https://issues.apache.org/jira/browse/FLINK-22275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22275:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> 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)
