[FEATURE REQ] Event Hubs: Lazy allocation of Properties and System Properties in EventData
See original GitHub issueLibrary or service name:
Azure.Messaging.EventHubs
Is your feature request related to a problem? Allow publishing EventData-objects without allocating Dictionary for SystemProperties
Current Workaround:
private class EventDataLight : EventData
{
static readonly IReadOnlyDictionary<string, object> DefaultSystemProperties = new Dictionary<string, object>();
public EventDataLight(byte[] eventBody, string partitionKey)
:base(eventBody, null, DefaultSystemProperties, partitionKey: partitionKey)
{
}
}
Worked in previous version
Microsoft.Azure.EventHubs
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
EventData.Properties Property (Azure.Messaging. ...
The set of free-form properties which may be used for associating metadata with the event that is meaningful within the application context.
Read more >[FEATURE REQ] Make EventData.SystemProperties with ...
The behavior that you're describing is by-design; the system properties are owned by the Event Hubs broker and are not intended to be...
Read more >EventData.SystemProperties Property
These properties are read-only and will only be populated for events that have been read from Event Hubs. The default value when not...
Read more >Class EventData | Azure SDK for Net
The set of free-form event properties which may be used for passing metadata associated with the event with the event body during Event...
Read more >.NET Core v2 Azure Function EventHub PartitionKey doesn ...
I'm unable to effectively set the PartitionKey property when using an Azure Function v2 (.NET Core). Firstly, I am unsure how I am...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
closed by #19876
No I’m very happy with the implementation of lazy-allocation. Thank you for the fast turn-around.