Yes, I think you're right. This bug appeared after we switched from
the Pulsar Admin API to the Pulsar Client API. Currently, the
connector doesn't check the existing subscription position. I
apologize for this regression. We need to add tests and implement a
fix. Since this is relatively easy to
I agree with you. It's quite useful to access the ExecutionConfig in
Source API. When I develop the flink-connector-pulsar. The only
configuration that I can't access is the checkpoint configure which is
defined in ExecutionConfig. I can switch the behavior automatically by
the checkpoint switch.
Hi Neng,
Thanks for reminding me of the need to explain the lack of
functionality. I have checked the missing functions with the customer
and teammates. And we found that the only function we can't support
after removing the Shared and Key_Shared subscription support is
delayed message delivery
