search

Azure / azure-sdk-for-net

This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
MIT License
5.57k stars 4.83k forks source link

[Feature Request] Compacted Eventhub Events with EntityKey and PartitionKey #38964

Closed AJosephsen closed 1 year ago

AJosephsen commented 1 year ago

Library name

Azure.Messaging.EventHubs

Please describe the feature.

Send events with a partition key to a specific partition (set both PartitionKey and PartitionID)

Or be able to specify a PartitionKey and EntityKey

Example we want all Account entities to be partitioned by ClientKey, so that all accounts for the same client are on the same partition. At the same time we compaction to happen on the AccountKey so that we only store the latest Account Event

jsquire commented 1 year ago

Hi @AJosephsen. Thank you for your feedback and we regret that you're experiencing difficulties. The limitation of being unable to publish an event using both the partition identifier and key is due to how the Event Hubs service works and is not something that the client library can influence. Compaction itself requires that events be published using a partition key which, again, is service behavior and not something under control of the client.

Because your inquiry is regarding behavior of the Event Hub service, your best path forward would be to open an Azure support request or use the Event Hubs topic of the Azure Feedback site to make a feature suggestion.

github-actions[bot] commented 1 year ago

Hi @AJosephsen. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

github-actions[bot] commented 1 year ago

Hi @AJosephsen, since you haven’t asked that we /unresolve the issue, we’ll close this out. If you believe further discussion is needed, please add a comment /unresolve to reopen the issue.