Bindings not working
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
Research direction
Start from the run function and its ServiceBusQueueTrigger and BindingName parameters. Compare the requested names—ApplicationProperties, DeliveryCount, deadLetterSource, and status—with the metadata exposed by the Java binding and the dead-letter message properties described in the issue. Reproduce the binding error with one uncommented parameter and determine which metadata names are supported.
Written by the indexing model from the issue text.
Description
I have a function using QueueTrigger and I want to get some metadata info:
@FunctionName("func-name")
public void run(
@ServiceBusQueueTrigger(
name = "message",
queueName = "%SERVICE_BUS_QUEUE_NAME%",
connection = "some connection details"
) String message,
//@BindingName("ApplicationProperties") Map<String, String> applicationProperties,
//@BindingName("DeliveryCount") int deliveryCount,
@BindingName("MessageId") String messageId,
//@BindingName("deadLetterSource") String deadLetterSource,
//@BindingName("status") String status,
final ExecutionContext context
)
The only data that I'm able to retrieve is the message MessageId. If I uncomment any of the other bindings, I get the following error:
Cannot find matched @BindingName of customer function, please check if customer function is defined correctly
But when I go to the queue and select a message and go to the tab Message Properties, I can see the properties but for some reason I'm not able to get it. Any hints of what might be?
I see the properties from the Dead letter queue and I'm resending the message to the queue.
- Dominant language
- Java
- Stars
- 45
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/azure-functions-java-library
-
area:java-functions
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Azure/azure-functions-java-library#229 · 1 comment ·
-
area:java-functions
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/azure-functions-java-library#222 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
area:java-functions
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
area:java-functions
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in Azure/azure-functions-java-library
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Content
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
RunestoneInteractive/rs#1559 · 1 comment ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
inu-appcenter/memorIN-backend#298 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
opendataloader-project/opendataloader-pdf#757 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
redhat-developer/intellij-quarkus#1626 ·