Having multiple EventHub outputs doesn't work as expected

[danielhertzman]

Hello!

We are using an Azure Function to receive and distinct each message based on a Property on the message. The message should then be sent out to two different EventHubs (which is set as output binding attributes) based on the Property.

Repro steps

Steps to reproduce the issue:

1. Create an Azure Function that will trigger on EventHub message

2. Output the messages further to two different EventHubs based on a message property on the EventData input.

Expected behavior

Expected behaviour is that these messages are being routed to each respective EventHub.

Actual behavior

The EventHub output as configured "first" in the Run() parameter is receiving all events.

Related information

As a proof of this issue, I'm providing you with an example project, containing the core routing functionality we are trying to implement.

It contains of an Azure Function that triggers on an EventHub and then sends them further using the IAsyncCollector. The project also contains two additional Azure Functions which is triggered on the two output EventHubs. The result is that only the first Azure Function is being triggered (the one called EH1Receiver)

Link to example project: https://github.com/danielhertzman/eventhub-trigger-example

[brettsam]

@alrod -- any idea on this one? Seems like a bug somewhere in how we set up the output bindings.

[alrod]

414f0a5