AVRO deserialization fails on Service Bus Subscription Trigger to Azure Function #19759
Comments
ghost
added
needs-triage
|
If anyone is still suffering from passing binary data to Azure triggered Functions, you need to add this parameter... {
"bindings": [
{
"name": "mySbMsg",
"type": "serviceBusTrigger",
+ "dataType": "binary",
"direction": "in",
"topicName": "%TOPIC_NAME%",
"subscriptionName": "%ONBOARDING_DATA_SUBSCRIPTION_NAME%",
"connection": "SERVICEBUS_CONNECTION_STRING"
}
],
"scriptFile": "../dist/OnboardingDataTrigger/index.js"
}I think the documentation here https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus-trigger?tabs=javascript#configuration should be improved to document this field. Thanks |
ramya-rao-a
added
Client
ghost
removed
the
needs-triage
|
@Axel92Dev Thanks for your report! Do I understand correctly that this is no longer an issue based on your comment in #19759 (comment)? |
Yes, it is not a problem for me anymore. But if you don't add this information in your docs, the next developer who tries to pass binary data on service bus will struggle for days. Thanks |
deyaaeldeen
added
the
issue-addressed
|
Hi @Axel92Dev. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “ |
|
Thanks for the feedback @Axel92Dev ! cc @shreyabatra4 |
|
Hi @Axel92Dev, since you haven’t asked that we “ |
Describe the bug
We are using Azure Service Bus (topic/subscription) to decouple a producer which is a Java Microservice and a consumer which is a Node/Typescript Azure Function.
The AF is triggered everytime a message arrives on a particular subscription.
Although we are not using Event Hubs, we created one to use the Schema Registry as we want to use AVRO as protocol for the messages exchanged on service bus.
For simple AVRO Message, it works fine by just passing the Uint8Array conversion of the message received:
const received = await serializer.deserialize(new Uint8Array(Buffer.from(serviceBusMessage)));But with a more complex AVRO message, it seems the byte array produced by the Java application and sent to the service bus is not the same we get when we parse the triggered message.
To Reproduce
Steps to reproduce the behavior:
application/octect-stream(we triedavro/binarywith same results, changed it as suggested here )avsca. the AVRO Schema as defined on the Schema Registry
b. arr2 which is the byte array I get from the Java Log of the producer
c. arr3 which is the byte array I get in my Azure Function using
JSON.stringify(Object.values(Buffer.from(serviceBusMessage))Expected behavior
arr3 should be equal to arr2 and be correctly parsed.
Arr2 is correctly parsed, it seems the Serivce Bus is doing something wrong with the message before invoking the Azure Function.
Screenshots
Additional context
This is the Azure Function code
This is the parsing code:
Already asked help to
avscmaintainer with helped me but no luck in solving it: mtth/avsc#376Thanks a lot
The text was updated successfully, but these errors were encountered: