You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently only a fixed set of system properties from Azure IoT Hub are forwarded as headers when delivered to a subscriber. The Azure Event Hubs binding should expose a getAllProperties property (false by default) to forward all user/app/custom properties from the Event Hub message as headers to the subscriber.
It seems that is 90% supported already in the DAPR codebase, but it stops short at exposing the setting in the manifest. i.e.
// GetBindingsHandlerFunc returns the handler function for bindings messagesfunc (aeh*AzureEventHubs) GetBindingsHandlerFunc(topicstring, getAllPropertiesbool, handler bindings.Handler) HandlerFn {
returnfunc(ctx context.Context, messages []*azeventhubs.ReceivedEventData) ([]HandlerResponseItem, error) {
iflen(messages) !=1 {
returnnil, fmt.Errorf("expected 1 message, got %d", len(messages))
}
bindingsMsg, err:=NewBindingsReadResponseFromEventData(messages[0], topic, getAllProperties)
iferr!=nil {
returnnil, fmt.Errorf("failed to get bindings read response from azure eventhubs message: %w", err)
}
aeh.logger.Debugf("Calling app's handler for message %s on topic %s", messages[0].SequenceNumber, topic)
_, err=handler(ctx, bindingsMsg)
returnnil, err
}
}
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered:
Describe the feature
Currently only a fixed set of system properties from Azure IoT Hub are forwarded as headers when delivered to a subscriber. The Azure Event Hubs binding should expose a
getAllProperties
property (false
by default) to forward all user/app/custom properties from the Event Hub message as headers to the subscriber.It seems that is 90% supported already in the DAPR codebase, but it stops short at exposing the setting in the manifest. i.e.
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered: