feat: add MongoDB functions to handle transactions #96
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Patricia Reinoso <[email protected]>
Signed-off-by: Patricia Reinoso <[email protected]>
|
HI @patriciareinoso - Where you plan to use the transaction feature? |
Hi @thakurajayL omec-project/webconsole#279 We are trying to ensure consistency in the DB after a DELETE operation. In the PR we would like to DELETE the reference to the gNB or UPF in a Network Slice after they are deleted. The idea is to do this also when deleting a Subscriber (-> remove the reference in the "imsis" list of Device Groups) and deleting Device Groups (-> remove the reference in the "site-device-group" list of Network Slices) |
thakurajayL
approved these changes
Jan 15, 2025
thakurajayL
pushed a commit
that referenced
this pull request
Jan 16, 2025
* add MongoDB functions to handle transactions Signed-off-by: Patricia Reinoso <[email protected]> * rename to supports transactions Signed-off-by: Patricia Reinoso <[email protected]> --------- Signed-off-by: Patricia Reinoso <[email protected]> Signed-off-by: Ajay Lotan Thakur <[email protected]>
gab-arrobo
pushed a commit
that referenced
this pull request
Jan 16, 2025
* Updates in the logs Signed-off-by: Ajay Lotan Thakur <[email protected]> * Bump github.com/gin-contrib/cors in /mongoapi/dbtestapp (#94) Signed-off-by: Ajay Lotan Thakur <[email protected]> * Fixing API errors Signed-off-by: Ajay Lotan Thakur <[email protected]> * Update drsm/api.go Co-authored-by: gab-arrobo <[email protected]> Signed-off-by: Ajay Lotan Thakur <[email protected]> * Update drsm/api.go Co-authored-by: gab-arrobo <[email protected]> Signed-off-by: Ajay Lotan Thakur <[email protected]> * Update drsm/api.go Co-authored-by: gab-arrobo <[email protected]> Signed-off-by: Ajay Lotan Thakur <[email protected]> * Update drsm/chunk.go Co-authored-by: gab-arrobo <[email protected]> Signed-off-by: Ajay Lotan Thakur <[email protected]> * Update drsm/claim.go Co-authored-by: gab-arrobo <[email protected]> Signed-off-by: Ajay Lotan Thakur <[email protected]> * Fix typo and update logging level Signed-off-by: Ajay Lotan Thakur <[email protected]> * feat: add MongoDB functions to handle transactions (#96) * add MongoDB functions to handle transactions Signed-off-by: Patricia Reinoso <[email protected]> * rename to supports transactions Signed-off-by: Patricia Reinoso <[email protected]> --------- Signed-off-by: Patricia Reinoso <[email protected]> Signed-off-by: Ajay Lotan Thakur <[email protected]> * Update drsm/api.go Co-authored-by: gab-arrobo <[email protected]> Signed-off-by: Ajay Lotan Thakur <[email protected]> --------- Signed-off-by: Ajay Lotan Thakur <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds 4 functions needed to handle transactions in mongoDB.
We would like to use transactions to ensure Atomicity in operations that perform 2 or more actions over the DB. With transactions, the operations are rolled back in case of failure. https://www.mongodb.com/docs/manual/core/transactions/
Transactions can only be used in Replica Set or sharded deployments.
Operations in a transaction use a shared
mongo.SessionContextinstead of separatecontext.TODO()