You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yufan Sheng (Jira)" <ji...@apache.org> on 2022/06/15 21:46:00 UTC
[jira] [Updated] (FLINK-28084) Pulsar unordered reader should disable retry and delete reconsume logic.
[ https://issues.apache.org/jira/browse/FLINK-28084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yufan Sheng updated FLINK-28084:
--------------------------------
Description: UnroderdPulsarSourceReader currently calls reconsume, but this feature relys on retry topic. But if retry topic is enabled the initial search will only support earliest and lates (because it will be a multiconsumer impl). We plan to delete the reconsume logic to get rid of dependency on retry topic and should disable retry. (was: Pulsar unordered reader is used for Shared and Key_Shared subscriptions. It would reconsume a message if it didn't acknowledge in a transaction. But this didn't works now. Because we don't use Pulsar's Multiple consumer. The best way to solve this problem is just delete this reconsumeLater logic.)
> Pulsar unordered reader should disable retry and delete reconsume logic.
> ------------------------------------------------------------------------
>
> Key: FLINK-28084
> URL: https://issues.apache.org/jira/browse/FLINK-28084
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
> Affects Versions: 1.15.0, 1.14.4
> Reporter: Yufan Sheng
> Priority: Major
> Fix For: 1.16.0
>
>
> UnroderdPulsarSourceReader currently calls reconsume, but this feature relys on retry topic. But if retry topic is enabled the initial search will only support earliest and lates (because it will be a multiconsumer impl). We plan to delete the reconsume logic to get rid of dependency on retry topic and should disable retry.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)