[
https://issues.apache.org/jira/browse/FLINK-30200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mason Chen updated FLINK-30200:
-------------------------------
Description:
Currently, the TimestampOffsetsInitializer defaults to `LATEST` and it would be
beneficial to allow the user to customize this to `EARLIEST` or `NONE`. This
was brought up in PR review:
[https://github.com/apache/flink/pull/20370#discussion_r991928769]
NOTE: this is a public API change albeit small, so we need to discuss on the
mailing list first.
was:Currently, the TimestampOffsetsInitializer defaults to `LATEST` and it
would be beneficial to allow the user to customize this to `EARLIEST` or
`NONE`. This was brought up in PR review:
https://github.com/apache/flink/pull/20370#discussion_r991928769
> TimestampOffsetsInitializer allows configurable OffsetResetStrategy
> -------------------------------------------------------------------
>
> Key: FLINK-30200
> URL: https://issues.apache.org/jira/browse/FLINK-30200
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Affects Versions: 1.16.0
> Reporter: Mason Chen
> Priority: Major
>
> Currently, the TimestampOffsetsInitializer defaults to `LATEST` and it would
> be beneficial to allow the user to customize this to `EARLIEST` or `NONE`.
> This was brought up in PR review:
> [https://github.com/apache/flink/pull/20370#discussion_r991928769]
> NOTE: this is a public API change albeit small, so we need to discuss on the
> mailing list first.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
