MonsterChenzhuo commented on a change in pull request #17994:
URL: https://github.com/apache/flink/pull/17994#discussion_r782225107
##########
File path:
flink-connectors/flink-connector-kafka/src/main/java/org/apache/flink/streaming/connectors/kafka/table/KafkaConnectorOptions.java
##########
@@ -158,6 +158,13 @@
.withDescription(
"Optional offsets used in case of
\"specific-offsets\" startup mode");
+ public static final ConfigOption<String> SCAN_BOUNDED_SPECIFIC_OFFSETS =
+ ConfigOptions.key("scan.bounded.specific-offsets")
+ .stringType()
+ .noDefaultValue()
+ .withDescription(
+ "When all partitions have reached their stop
offsets, the source will exit");
+
public static final ConfigOption<Long> SCAN_STARTUP_TIMESTAMP_MILLIS =
Review comment:
Hi @ruanhang1993 Bounded `offset` and timestamp, I can understand it
like this
By specifying a bounded `offset` let the program consume to the end of the
specified position, and by specifying a timestamp let the program consume to
the end of the specified timestamp position, but I don't understand what role
does `latest-offset` play in the current bounded case? What kind of semantics
does it play. I can set `latest-offset` with `scan.startup.mode`.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
