[
https://issues.apache.org/jira/browse/FLINK-27399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yufan Sheng updated FLINK-27399:
--------------------------------
Description:
The Pulsar connector didn't use the consuming position from the checkpoint.
They just commit the position to Pulsar after the checkpoint is complete. And
the connector start to consume message from Pulsar directly by the offset
stored on the Pulsar subscription.
This causes the test could be failed in some situations. The start cursor would
be reset to the wrong position which causes the results didn't match the
desired records.
This issue blocks
# FLINK-23944
# FLINK-25884
# FLINK-26177
# FLINK-26237
# FLINK-26721
Although the test failure message could be various. They are truly sharing the
same cause.
was:
The Pulsar connector didn't use the consuming position from the checkpoint.
They just commit the position to Pulsar after the checkpoint and start
consuming from it directly.
This causes the test could be failed in some situations. The start cursor would
be reset to the wrong position which causes the results didn't match the
desired records.
This issue blocks
# FLINK-23944
# FLINK-25884
# FLINK-26177
# FLINK-26237
# FLINK-26721
Although the test failure message could be various. They are truly sharing the
same cause.
> Pulsar connector didn't set start consuming position correctly
> --------------------------------------------------------------
>
> Key: FLINK-27399
> URL: https://issues.apache.org/jira/browse/FLINK-27399
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
> Affects Versions: 1.15.0, 1.14.4, 1.16.0
> Reporter: Yufan Sheng
> Assignee: Yufan Sheng
> Priority: Major
> Fix For: 1.16.0, 1.14.5, 1.15.1
>
>
> The Pulsar connector didn't use the consuming position from the checkpoint.
> They just commit the position to Pulsar after the checkpoint is complete. And
> the connector start to consume message from Pulsar directly by the offset
> stored on the Pulsar subscription.
> This causes the test could be failed in some situations. The start cursor
> would be reset to the wrong position which causes the results didn't match
> the desired records.
> This issue blocks
> # FLINK-23944
> # FLINK-25884
> # FLINK-26177
> # FLINK-26237
> # FLINK-26721
> Although the test failure message could be various. They are truly sharing
> the same cause.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
