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

[Service Bus] Transactions #8252

Closed
shlomiassaf opened this issue Apr 7, 2020 · 6 comments
Closed

[Service Bus] Transactions #8252

shlomiassaf opened this issue Apr 7, 2020 · 6 comments
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. Service Bus
Milestone

Comments

@shlomiassaf
Copy link

Is there any plan to support transactions?

@xirzec xirzec added Client This issue points to a problem in the data-plane of the library. Service Bus labels Apr 7, 2020
@triage-new-issues triage-new-issues bot removed the triage label Apr 7, 2020
@xirzec xirzec added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Apr 7, 2020
@ramya-rao-a
Copy link
Contributor

Are you referring to the feature as described in https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-transactions?

We are considering support for transactions for the next version of the @azure/service-bus package a few months down the line. Can you elaborate on how this feature is helpful in your application?

@ramya-rao-a ramya-rao-a added the feature-request This issue requires a new behavior in the product in order be resolved. label Apr 8, 2020
@ramya-rao-a ramya-rao-a added this to the [2020] June milestone Apr 8, 2020
@shlomiassaf
Copy link
Author

shlomiassaf commented Apr 8, 2020

@ramya-rao-a yes, I’m referring to that feature.

There are a lot of scenarios of course.
For example, we have a backoff and retry mechanized which is pseudo random with an exponential delay period between retries.
When a retry is set, we clone the message and emit it with the delay calculated.
This operation requires emitting a new message while completing the current one which threw an error while being handled.

The only way for us to be sure it’s done right is having both operations atomic.

@ramya-rao-a ramya-rao-a modified the milestones: [2020] June, Backlog May 11, 2020
@Petermarcu
Copy link
Member

@ramya-rao-a is this backlog still or something going into the next version?

@ramya-rao-a
Copy link
Contributor

Yes, this is in the Backlog as the milestone hints :)
Both in Python & JS, we plan to pick this up once the current version 7 of the Service Bus package moves out of preview.

@ramya-rao-a
Copy link
Contributor

An update based on current investigations:

Looks like rhea, the underlying AMQP library we use for Service Bus does not support the transactions feature. Therefore, we need first invest time in adding support there and then get back to the Service Bus package to utilize this AMQP feature. This issue will continue to be in our backlog for now until the support is added to rhea

Copy link

Hi @shlomiassaf, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. Service Bus
Projects
Status: Done
Development

No branches or pull requests

5 participants