You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2022. It is now read-only.
Describe the bug
I want to consume a pulsar topic from latest offset of a subcription, and I try to use the code below
FlinkPulsarSource<String> flinkPulsarSource =
new FlinkPulsarSource<String>(
serviceUrl,
adminUrl,
new PulsarRecordDeserializeSchema(),
properties).setStartFromSubscription(groupid_antisdk, MessageId.latest);
and when restart the flink job, it consume from the subscritpion offset commited before, not the latest.
and then I try to use startFromLatest method, the code as below
FlinkPulsarSource<String> flinkPulsarSource =
new FlinkPulsarSource<String>(
serviceUrl,
adminUrl,
new PulsarRecordDeserializeSchema(),
properties).setStartFromLatest();
but the subscription name is a random string generated by connector, not we specified by pulsar.reader.subscriptionRolePrefix
To Reproduce
reproduce this problem as described above
Expected behavior
by use setStartFromSubscription(groupid_antisdk, MessageId.latest) we can start from latest offset of a subscription.
Screenshots
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
I want to consume a pulsar topic from latest offset of a subcription, and I try to use the code below
and when restart the flink job, it consume from the subscritpion offset commited before, not the latest.
and then I try to use
startFromLatest
method, the code as belowbut the subscription name is a random string generated by connector, not we specified by
pulsar.reader.subscriptionRolePrefix
To Reproduce
reproduce this problem as described above
Expected behavior
by use setStartFromSubscription(groupid_antisdk, MessageId.latest) we can start from latest offset of a subscription.
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: