[
https://issues.apache.org/jira/browse/FLINK-32021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonard Xu resolved FLINK-32021.
--------------------------------
Resolution: Fixed
Resolved in flink-connector-kafka(main):
14d8462be33c25031e94da0635105f69bb807641
> Improvement the Javadoc for SpecifiedOffsetsInitializer and
> TimestampOffsetsInitializer.
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-32021
> URL: https://issues.apache.org/jira/browse/FLINK-32021
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Kafka
> Affects Versions: kafka-3.0.0
> Reporter: Hongshun Wang
> Assignee: Hongshun Wang
> Priority: Minor
> Labels: pull-request-available
> Fix For: kafka-4.0.0
>
>
> As described in
> [FLIP-288|https://cwiki.apache.org/confluence/display/FLINK/FLIP-288%3A+Enable+Dynamic+Partition+Discovery+by+Default+in+Kafka+Source],
> Current JavaDoc does not fully explain the behavior of OffsetsInitializers.
> When the partition does not meet the condition, there will be a different
> offset strategy. This may lead to misunderstandings in the design and usage.
>
> Add to SpecifiedOffsetsInitializer: "Use Specified offset for specified
> partitions while use commit offset or Earliest for unspecified partitions.
> Specified partition offset should be less than the latest offset, otherwise
> it will start from the earliest."
>
> Add to TimestampOffsetsInitializer:Initialize the offsets based on a
> timestamp. If the message meeting the requirement of the timestamp have not
> been produced to Kafka yet, just use the latest offset.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
