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.

Sign up for GitHub

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

Jump to bottom

Exception thrown for handlers that do not use synchronized storage #86

Closed
danielmarbach opened this issue Oct 23, 2020 · 2 comments · Fixed by #87 or #88
Closed

Exception thrown for handlers that do not use synchronized storage #86

danielmarbach opened this issue Oct 23, 2020 · 2 comments · Fixed by #87 or #88
Labels
bug Something isn't working
Milestone
0.1.1

Comments

@danielmarbach
Copy link
Contributor

danielmarbach commented Oct 23, 2020 •
edited
Loading

Who's affected

  • All customers using the persistence

Symptoms

For cases when a message is destined to go to a handler that doesn't use CosmosDB a synchronized storage session is still created behind the scenes. In such cases it is not necessary to provide the container information yet is is enforced by us and an exception is thrown

Unable to retrieve the container name and the partition key during processing. Make sure that either persistence.Container() is used or the relevant container information is available on the message handling pipeline.

Backported to
@danielmarbach danielmarbach added the bug Something isn't working label Oct 23, 2020
@danielmarbach danielmarbach mentioned this issue Oct 23, 2020
Merged
@boblangley boblangley added this to the 0.1.1 milestone Oct 23, 2020
@boblangley boblangley linked a pull request Oct 23, 2020 that will close this issue
Make container information non-mandatory for handlers that don't require storage access #88
Merged
@boblangley boblangley changed the title Unable to retrieve the container name exception thrown for empty handlers Unable to retrieve the container name exception thrown for handlers that do not use synchronized storage Oct 23, 2020
@boblangley boblangley changed the title Unable to retrieve the container name exception thrown for handlers that do not use synchronized storage Exception thrown for handlers that do not use synchronized storage Oct 23, 2020
@boblangley
Copy link
Member

We triaged this issue as critical and will release a patch release as soon as possible.

@boblangley
Copy link
Member

boblangley commented Oct 23, 2020 •
edited
Loading

The 0.1.1 version with this fix has been pushed to NuGet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
0.1.1
2 participants
@danielmarbach @boblangley