[jira] [Commented] (FLINK-26614) Upsert Kafka SQL Connector:Support startup mode of timestamp and specific offsets

["Martijn Visser (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-26614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511116#comment-17511116 ] 

Martijn Visser commented on FLINK-26614:
----------------------------------------

[~ningma] Thanks for opening the ticket and the PR. I've downgraded the ticket to Major, since only bugs can be a Blocker per Flink's Jira process https://cwiki.apache.org/confluence/display/FLINK/Flink+Jira+Process

> Upsert Kafka SQL Connector:Support startup mode of timestamp and specific offsets
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-26614
>                 URL: https://issues.apache.org/jira/browse/FLINK-26614
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kafka
>    Affects Versions: 1.14.4
>            Reporter: Ning Ma
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.14.5
>
>
> When we run Flink SQL using upsert-kafka connector, it cannot support startup mode of timestamp or specific offsets. It is determined to read data from the earliest.
> I don't think it's reasonable. Because the data stored in Kafka is incomplete that it only saves data for 7 days in most cases. So why don't we consume data from the specified timestamp or offsets, and this can improve the efficiency of reading data from Kafka.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)