[
https://issues.apache.org/jira/browse/FLINK-22275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325656#comment-17325656
]
Jark Wu commented on FLINK-22275:
---------------------------------
Personally, this sounds like an out-of-order configuraiton to me and only
applied to timestamp type. Thus, would be better to use {{Duration}} type,
rather than {{Integer}} type.
I also checked other systems, such as [java
facker|http://dius.github.io/java-faker/apidocs/index.htm5sl], it provodes an
API {{DateAndTime#past}} to support this.
So I think maybe {{fields.atime.max-past=5s}} would be clearer, and better for
future evolution, e.g. support {{fields.atime.max-future=5s}} in the future.
> 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
> Priority: Minor
>
> 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)
