Query/Question
Sorry if I'm asking in the wrong location.
All the documentation for Azure Functions (and the Visual Studio Template) use the Microsoft.Azure.WebJobs.Extensions.EventHubs nuget package to setup an EventHubTrigger, but that's using the Microsoft.Azure.EventHubs nuget package.
Is there a new sdk that contains the EventHubTrigger?
Thanks!
Environment:
dotnet --info output for .NET Core projects): Azure V3 FunctionHi @willyt150. The triggers and bindings for Azure Functions take a dependency on the client libraries for other services - meaning, that the Event Hubs library wouldn't offer any constructs specific to the Functions environment, rather the EventHubTrigger would need to make the decision to consume v5.x of the Event Hubs client.
To my knowledge, the Functions bindings have not yet been updated to the new line of Azure SDKs. @pakrym may have some additional insight that he's able to provide from discussion with the Azure Functions team.
Ok thanks @jsquire! One more question, do you happen to know if there are any issues using the 5.1 Event Hubs library to send event data and the old library and a function trigger/binding to read the data? I'm asking because we've run into issues with the v12 Storage Queues library and the v11 function trigger where the message had to be base64 encoded before it was sent otherwise the function trigger would blow up.
And I guess I'll be sticking with the old libraries for now then because of my functions.
do you happen to know if there are any issues using the 5.1 Event Hubs library to send event data and the old library and a function trigger/binding to read the data?
I do; You should be able to cross the v4 and v5 versions of Event Hubs when publishing and consuming without issue. The event message formats are compatible between them.
Yes, we are working on a new set of WebJobs extensions based on the new libraries. Unfortunately, it's a bit early for me to be able to name exact dates but it's coming.
alright, hopefully that will come sooner rather than later :) (as with all things programming)
Thank you for answering my question.