[
https://issues.apache.org/jira/browse/FLINK-26614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26614:
-----------------------------------
Labels: auto-deprioritized-major pull-request-available stale-minor (was:
auto-deprioritized-major pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: New Feature
> Components: Connectors / Kafka
> Affects Versions: 1.14.4
> Reporter: Ning Ma
> Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available,
> stale-minor
>
> 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.10#820010)
