This message was deleted.
# generals
Slackbot
10/23/2023, 1:42 PMThis message was deleted.
j
James
10/23/2023, 2:18 PMI don't think I understand what you're asking, but if I do, why not just use a consumer that nacks every message?
d
Dheeraj Dixit
10/23/2023, 2:30 PMwe dont want to use consumer interface as it will interfere with actual message consumption from client( could impact performance). Also, consumer interface wont work in case of exclusive subscription type as only one consumer is allowed to be connected and we wont be able to read messages if a consumer is already connected and consuming.
j
James
10/23/2023, 2:49 PMok so I think I do understand. If it's possible to know the first backlog message id for your subscription, you can use a reader with that message id as the starting point.
James
10/23/2023, 2:50 PMI'm new to pulsar so I'm not sure how to get that message id.
d
Dheeraj Dixit
10/23/2023, 3:03 PMwe explored reader interface as well, Its for reading messages from topic not subscription. Also, not sure it will work with partition topic, I read somewhere it wont work for partitioned topics( I know Reader.seek() only works for Non-partitioned topics).
a
Asaf Mesika
10/24/2023, 11:49 AMHmmm, seems like you want to know the metadata of a subscription, and read the messages “from the side” on a different subscription or even non-durable subscription, just to display the messages which are yet to be acknoweldged. Is that correct?
Asaf Mesika
10/24/2023, 11:50 AMRead would give you the ability to read and you can pinpoint it per entryId, so the only thing you’re missing is getting the up-to-date subscription data
Asaf Mesika
10/24/2023, 12:20 PMYou can use InternalStats for a topic (vis Pulsar Admin) - this will give information per subscription (named cursor internally). There you can see both the markDelete (the position which before all messages have been acked) and also the individual ack message ranges.
4 Views