Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session Enabled Queue Message Properties Not Being Populated #558

Closed
theclouditect opened this issue Oct 2, 2019 · 5 comments
Closed

Session Enabled Queue Message Properties Not Being Populated #558

theclouditect opened this issue Oct 2, 2019 · 5 comments
Assignees
Labels
Milestone

Comments

@theclouditect
Copy link

When using Azure Service Bus Queues that are session enabled the ServiceBusMessage object is not completely populated. The message_id and message_body are populated, but all other properties are null. This is using a ServiceBusTrigger input binding. The C# version of this function works fine and properties are populated.

Repro steps

1.) Create Python Function App + Azure Service Bus Queue with sessions enabled
2.) Update ServiceBusExtension to 3.1.0 in extensions.csproj
3.) Add "isSessionsEnabled" : true to function.json
4.) Add code in function to log session_id or other properties on the input binding
5.) Put message onto Queue.

Expected behavior

Properties will be populated with properties of message that was put onto the queue.

Actual behavior

1.) Logging will show the correct SessionId in a log message that starts with "Trigger Details:"
2.) Logging message added in code will show properties are null except for message_id and body.

Known workarounds

No known workarounds

Related information

Provide any related information

  • Links to source
  • Contents of the requirements.txt file
  • Bindings used

image
image

@anirudhgarg anirudhgarg added this to the Triaged milestone Oct 10, 2019
@anirudhgarg
Copy link
Member

@Hazhzeng can you have a look at this. We have gotten another CRI for this.

@vinodc
Copy link

vinodc commented Jun 23, 2020

We're running into this issue as well. Has there been any progress on identifying a potential solution?

@anirudhgarg
Copy link
Member

hello folks - we have identified the missing properties and we are working on adding these. These changes should be rolled out in 3-4 weeks if not earlier.

@Hazhzeng
Copy link
Contributor

Sorry for the late reply. The fix has been rolled-out in last years July. Closing this issue now.
If you have any other questions, please open a new issue.

@sidkri
Copy link
Member

sidkri commented Feb 9, 2022

It looks like this is still an issue and I created a new issue to track the fix: Azure/azure-functions-python-library#103

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants