Tombstone events in Azure Event Hub for Log Compacted Topics #37463
Labels
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Event Hubs
Messaging
Messaging crew
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Describe the bug
We want to use log compacted Event Hubs (see https://learn.microsoft.com/en-us/azure/event-hubs/use-log-compaction) with the python SDK. To use the full potential of the log compacted topics we need to be able to send tombstone events to indicate the end-of-life for a certain event indicated by its
partition_key
.We naively followed the documentation and tried to send an empty event with an existing
partition_key
likeHowever, the body of an event cannot be
None
. Therefore, the next best guess was to useEventData(b'')
. But this just sends and empty string and does not trigger the tombstone mechanic of the queue.To Reproduce
Steps to reproduce the behavior:
Create a log compacted eventhub with a retention for tombstone events of 1 hour.
Send a message with a
null
body (as mentioned in the documentation, linked above)Example code:
Expected behavior
After one hour, I would have expected the topic to be empty. However, the message with the empty body still remains in the topic.
Question
How to create an Event with a
null
body?The text was updated successfully, but these errors were encountered: