Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://learn.microsoft.com/en-us/azure/azure-functions/scripts/../functions-bindings-event-hubs below:

Azure Event Hubs bindings for Azure Functions

This article explains how to work with Azure Event Hubs bindings for Azure Functions. Azure Functions supports trigger and output bindings for Event Hubs.

The extension NuGet package you install depends on the C# mode you're using in your function app:

The functionality of the extension varies depending on the extension version:

• Extension v6.x+
• Extension v5.x
• Extension v3.x+
• Functions v1.x
• Extension v6.x+
• Extension v5.x
• Extension v3.x+
• Functions v1.x

This section describes using a class library. For C# scripting, you would need to instead install the extension bundle, version 4.x.

This version introduces the ability to connect using an identity instead of a secret. For a tutorial on configuring your function apps with managed identities, see the creating a function app with identity-based connections tutorial.

This version uses the newer Event Hubs binding type Azure.Messaging.EventHubs.EventData.

This extension version is available by installing the NuGet package, version 6.x.

This section describes using a class library. For C# scripting, you would need to instead install the extension bundle, version 3.x or later.

This version introduces the ability to connect using an identity instead of a secret. For a tutorial on configuring your function apps with managed identities, see the creating a function app with identity-based connections tutorial.

This version uses the newer Event Hubs binding type Azure.Messaging.EventHubs.EventData.

This extension version is available by installing the NuGet package, version 5.x.

This section describes using a class library. For C# scripting, you would need to instead install the extension bundle, version 2.x.

Supports the original Event Hubs binding parameter type of Microsoft.Azure.EventHubs.EventData.

Add the extension to your project by installing the NuGet package, version 3.x or 4.x.

Version 1.x of the Functions runtime doesn't require an extension.

This version introduces the ability to connect using an identity instead of a secret. For a tutorial on configuring your function apps with managed identities, see the creating a function app with identity-based connections tutorial.

This version supports configuration of triggers and bindings through .NET Aspire integration.

Add the extension to your project by installing the NuGet package, version 6.x.

This version introduces the ability to connect using an identity instead of a secret. For a tutorial on configuring your function apps with managed identities, see the creating a function app with identity-based connections tutorial.

This version supports configuration of triggers and bindings through .NET Aspire integration.

Add the extension to your project by installing the NuGet package, version 5.x.

Add the extension to your project by installing the NuGet package, version 4.x.

Version 1.x of the Functions runtime doesn't support running in an isolated worker process.

The Event Hubs extension is part of an extension bundle, which is specified in your host.json project file. You may need to modify this bundle to change the version of the binding, or if bundles aren't already installed. To learn more, see extension bundle.

• Bundle v4.x
• Bundle v3.x
• Bundle v2.x
• Functions v1.x

This version introduces the ability to connect using an identity instead of a secret. For a tutorial on configuring your function apps with managed identities, see the creating a function app with identity-based connections tutorial.

You can add this version of the extension from the extension bundle v4 by adding or replacing the following code in your host.json file:

{
    "version": "2.0",
    "extensionBundle": {
        "id": "Microsoft.Azure.Functions.ExtensionBundle",
        "version": "[4.0.0, 5.0.0)"
    }
}

To learn more, see Update your extensions.

This version introduces the ability to connect using an identity instead of a secret. For a tutorial on configuring your function apps with managed identities, see the creating a function app with identity-based connections tutorial.

You can add this version of the extension from the extension bundle v3 by adding or replacing the following code in your host.json file:

{
    "version": "2.0",
    "extensionBundle": {
        "id": "Microsoft.Azure.Functions.ExtensionBundle",
        "version": "[3.3.0, 4.0.0)"
    }
}

To learn more, see Update your extensions.

You can install this version of the extension in your function app by registering the extension bundle, version 2.x.

Version 1.x of the Functions runtime doesn't require extension bundles.

The binding types supported for .NET depend on both the extension version and C# execution mode, which can be one of the following options:

• Isolated worker model
• In-process model

An isolated worker process class library compiled C# function runs in a process isolated from the runtime.

An in-process class library is a compiled C# function runs in the same process as the Functions runtime.

Choose a version to see binding type details for the mode and version.

• Extension v6.x+
• Extension v5.x
• Extension v3.x+
• Functions v1.x
• Extension v6.x+
• Extension v5.x
• Extension v3.x+
• Functions v1.x

The Event Hubs extension supports parameter types according to the table below.

¹ Events containing JSON data can be deserialized into known plain-old CLR object (POCO) types.

The Event Hubs extension supports parameter types according to the table below.

¹ Events containing JSON data can be deserialized into known plain-old CLR object (POCO) types.

Earlier versions of the extension exposed types from the now deprecated Microsoft.Azure.EventHubs namespace. Newer types from Azure.Messaging.EventHubs are exclusive to Extension v5.x+.

This version of the extension supports parameter types according to the table below.

¹ Events containing JSON data can be deserialized into known plain-old CLR object (POCO) types.

Earlier versions of the extension exposed types from the now deprecated Microsoft.Azure.EventHubs namespace. Newer types from Azure.Messaging.EventHubs are exclusive to Extension v5.x+.

This version of the extension supports parameter types according to the table below.

¹ Events containing JSON data can be deserialized into known plain-old CLR object (POCO) types.

The isolated worker process supports parameter types according to the tables below. Support for binding to types from [Azure.Messaging.EventHubs] is in preview.

Event Hubs trigger

When you want the function to process a single event, the Event Hubs trigger can bind to the following types:

When you want the function to process a batch of events, the Event Hubs trigger can bind to the following types:

¹ To use these types, you need to reference Microsoft.Azure.Functions.Worker.Extensions.EventHubs 5.5.0 or later and the common dependencies for SDK type bindings.

Event Hubs output binding

When you want the function to write a single event, the Event Hubs output binding can bind to the following types:

When you want the function to write multiple events, the Event Hubs output binding can bind to the following types:

For other output scenarios, create and use an EventHubProducerClient with other types from Azure.Messaging.EventHubs directly. See Register Azure clients for an example of using dependency injection to create a client type from the Azure SDK.

The isolated worker process supports parameter types according to the tables below. Support for binding to types from [Azure.Messaging.EventHubs] is in preview.

Event Hubs trigger

When you want the function to process a single event, the Event Hubs trigger can bind to the following types:

When you want the function to process a batch of events, the Event Hubs trigger can bind to the following types:

¹ To use these types, you need to reference Microsoft.Azure.Functions.Worker.Extensions.EventHubs 5.5.0 or later and the common dependencies for SDK type bindings.

Event Hubs output binding

When you want the function to write a single event, the Event Hubs output binding can bind to the following types:

When you want the function to write multiple events, the Event Hubs output binding can bind to the following types:

For other output scenarios, create and use an EventHubProducerClient with other types from Azure.Messaging.EventHubs directly. See Register Azure clients for an example of using dependency injection to create a client type from the Azure SDK.

Earlier versions of the extension in the isolated worker process only support binding to strings and JSON serializable types. More options are available to Extension v5.x+.

Functions version 1.x doesn't support the isolated worker process. To use the isolated worker model, upgrade your application to Functions 4.x.

The host.json file contains settings that control behavior for the Event Hubs trigger. The configuration is different depending on the extension version.

• Extension v5.x/v6.x+
• Extension v3.x+
• Functions v1.x

{
    "version": "2.0",
    "extensions": {
        "eventHubs": {
            "maxEventBatchSize" : 100,
            "minEventBatchSize" : 25,
            "maxWaitTime" : "00:05:00",            
            "batchCheckpointFrequency" : 1,
            "prefetchCount" : 300,
            "transportType" : "amqpWebSockets",
            "webProxy" : "https://proxyserver:8080",
            "customEndpointAddress" : "amqps://company.gateway.local",
            "targetUnprocessedEventThreshold" : 75,
            "initialOffsetOptions" : {
                "type" : "fromStart",
                "enqueuedTimeUtc" : ""
            },
            "clientRetryOptions":{
                "mode" : "exponential",
                "tryTimeout" : "00:01:00",
                "delay" : "00:00:00.80",
                "maximumDelay" : "00:01:00",
                "maximumRetries" : 3
            }
        }
    }
}  

NOTE: This interval is not a strict guarantee for the exact timing on which the function is invoked. There is a small margin of error due to timer precision. When scaling takes place, the first invocation with a partial batch may occur more quickly or may take up to twice the configured wait time.

¹ Using minEventBatchSize and maxWaitTime requires v5.3.0 of the Microsoft.Azure.WebJobs.Extensions.EventHubs package, or a later version.

² The default maxEventBatchSize changed in v6.0.0 of the Microsoft.Azure.WebJobs.Extensions.EventHubs package. In earlier versions, this was 10.

The clientRetryOptions are used to retry operations between the Functions host and Event Hubs (such as fetching events and sending events). Refer to guidance on Azure Functions error handling and retries for information on applying retry policies to individual functions.

For a reference of host.json in Azure Functions 2.x and beyond, see host.json reference for Azure Functions.

{
    "version": "2.0",
    "extensions": {
        "eventHubs": {
            "batchCheckpointFrequency": 1,
            "eventProcessorOptions": {
                "maxBatchSize": 256,
                "prefetchCount": 512
            },
            "initialOffsetOptions": {
                "type": "fromStart",
                "enqueuedTimeUtc": ""
            }
        }
    }
}  

¹ Support for initialOffsetOptions begins with EventHubs v4.2.0.

For a reference of host.json in Azure Functions 2.x and beyond, see host.json reference for Azure Functions.

{
    "eventHub": {
      "maxBatchSize": 64,
      "prefetchCount": 256,
      "batchCheckpointFrequency": 1
    }
}

For a reference of host.json in Azure Functions 1.x, see host.json reference for Azure Functions 1.x.

• Respond to events sent to an event hub event stream (Trigger)
• Write events to an event stream (Output binding)

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4