Feature/autorelation transaction - #48
Merged
Merged
Conversation
…ective writes only Rename run to inTransaction, restore the join-without-retry and non-null explanations, fix the logger import, and remove the retry helper and unused transaction template from ResponseEventService. ResourceStore.applyAll now states its return type and documents that the returned list is only trustworthy inside a transaction. ResourceTimestamp sits next to ResourceIdentity.
ResourceStoreIT pins the returned list for stale saves, duplicate ids, stale deletes, deletes of missing ids and the millisecond boundary. AutoRelationIT covers an old and a new version in one batch and a stale tombstone. ResourceWritePipelineIT covers rollback when the edge write fails, a nested call joining the outer transaction, and an update or insert landing between the pre-read and the write.
jflatby
reviewed
Sep 16, 2026
jflatby
approved these changes
Sep 16, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Lagde en MongoTransactions klasse som har en hjelper funksjon som tar en funksjon og kjører den inni en MongoDB transaksjon. Om vi får en transient mongodb feil (en race condition på hvem som oppdaterer ressursen først) så prøver vi må nytt opp til 5 ganger.
ResourceWritePipeline tar i bruk MongoTransactions slik at relasjons kantene vi genererer basert på hvilken ressurser som ble lagd/slettet/oppdatert dukker opp samtidig i databasen.