Azure / Azure/azure-functions-host
Javascript Functions should default to "cardinality": "many" for EventHubs
- Dominant language
- C#
- Stars
- 2k
- Forks
- 482
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 38
Description
The default behavior that we recommend is to batch trigger events. However, we have it as an opt-in setting right now. We should change this so that best practice = default behavior
https://stackoverflow.com/questions/46204764/eventhub-trigger-to-functions-cardinality-with-one-causing-higher-timeouts
Docs on EventHubs settings: https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-hubs#trigger---configuration
Contributor guide
Research direction
Start with the Event Hubs trigger configuration documentation and the linked Stack Overflow discussion, then trace where the JavaScript Functions cardinality default is defined. Done means Event Hubs triggers default to cardinality "many" rather than requiring opt-in, with the configuration documentation updated if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100