`EventPosition::SequenceNumber` seems to still start from the beginning about azeventhubs HOT 2 CLOSED

Apologies, my repro is really vague. I'll spend some more time seeing if the issue is in my code. I'll close this and reopen if I have a clearer description.

from azeventhubs.

Hi @jackgerrits

I am not able to reproduce this behaviour. I have added a simple example consumer_read_from_position.rs which basically let the consumer read 30 events from the beginning, records the last known sequence number (ie. the sequence number of the 30th event), closes the stream, then call read_events_from_partition() again but with the recorded last known sequence number, and it seems to work just as expected. The partition was first populated with 300 events with the event_hub_producer_example.rs which contains a monotonically increasing number.

I have also tried closing the consumer client entirely and create a new one, which also works as expected. Could you let me know more about your configuration?

from azeventhubs.