[EventHubs] Finalize design on Idempotent Producer

[yunhaoling]

background

idempotent producer is targeted to solve the problem of sending duplicate messages and provide "exactly once delivery".
There has been a preview release for idempotent producer already which is available on the branch: https://github.com/Azure/azure-sdk-for-python/tree/feature/eventhub/idempotent-producer

• latest update: discussion postponed, currently no feature request from python users, more data is needed
• This issue also has something to do with the StreamingProducer Design: [EventHubs] Streaming Producer Design #18718.
  We need to take both into account when making design decision.
• The buffered producer design is settled, it's a question of how the idempotency works for buffered mode.
• There is an ongoing email thread for discussion within the team, so need to have a cross-language agreement on the two concepts/whether to support it/overall structure.

Another design topic would be: Idempotent Producer naming of *_published_sequence_number property on different Objects

we have two prefixs on *_published_sequence_number on EventDataBatch and EventHubProducerClient, and we have multiple opinions on the naming:

class EventDataBatch:
    def starting_published_sequence_number(self):
    # beginning/first/ or just published_sequence_number?

# `PartitionPublishingProperties` which is a dictionary returned by `EventHubProducerClient.get_partition_publishing_properties()`

dic['last_published_sequence_number']
# ending_published_sequence_number?

tasks

• sync up with Jesse/service team first, definite the scope

[jsquire]

@kashifkhan - If we can confirm there's a single option for "EnableIdempotentPartitions" that the buffered producer can use - then the design is final and we can kill this one. 😄

[github-actions]

Hi @yunhaoling, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.