Azure.Messaging.EventHubs.Processor_5.11.2
5.11.2 (2024-04-10)
Bugs Fixed
-
The
EventProcessorClient
will now create a unique span for each event emitted to the handler for processing. Previously a single span was created for all events in a batch. (#31922) -
Fixed a parameter ordering error in ETW 22 (EventBatchProcessingError) that caused structured data arguments to be ordered differently than the associated replacement token in the log message.
Other Changes
- Added option
EnableCheckpointing
to allow automatic checkpointing to be disabled for applications that only wish to read current data rather than tracking the state of processing.