mas-chen opened a new pull request, #20370:
URL: https://github.com/apache/flink/pull/20370
…ategy and handle timestamps that do not map to an offset
## What is the purpose of the change
This change improves the TimestampOffsetsInitializer to be initialized with
a configured offset reset strategy. The default behavior (LATEST) is preserved.
This also fixes a bug for when the timestamp does not correspond to an offset
in Kafka and clarifies the exception message that is thrown.
## Brief change log
- Handles EARLIEST/LATEST/NONE
- For timestamps that do not correspond to an offset in Kafka and if
configured with NONE, the initializer will throw an explicit exception.
## Verifying this change
This change added tests and can be verified as follows:
- Added unit test to test the various offset reset strategies and the edge
case where timestamp does not correspond to an offset in Kafka
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: yes
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? yes
- If yes, how is the feature documented? JavaDocs
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
