When this is the function definition, IAsyncCollector sends the message always to the very first out binding (in our case eventHubCollector1). I.e., eventHubCollector2 will not receive anything.
Version:
Azure Function v2
Microsoft.Azure.WebJobs.Extensions.EventHubs - v4.1.1
Hello Team,
We're noticing an issue when a function have a 2 EH outbuildings as below, and both having the same EH name, but onto the different EH namespace.
Code Snippet:
public async Task Run ( [ActivityTrigger] ActivityInput activity, [EventHub("EH1", Connection= "EH-namespace1")] IAsyncCollector<EventData> eventHubCollector1, [EventHub("EH1", Connection= "EH-namespace2")] IAsyncCollector<EventData> eventHubCollector2, ILogger log)
When this is the function definition, IAsyncCollector sends the message always to the very first out binding (in our case eventHubCollector1). I.e., eventHubCollector2 will not receive anything.
Version: Azure Function v2 Microsoft.Azure.WebJobs.Extensions.EventHubs - v4.1.1