You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating document, one entry in Documents container and many entry in Meta container is updated.
All those entry need to be updated atomically (either all are updated or none are updated).
Otherwise the 2 container will become out of sync if the service crash after calling HandleMetaAsync but before updating the Document container.
How can this be designed to not leave the data in the DB corrupted?
The text was updated successfully, but these errors were encountered:
this would be CosmosDB.
And by "corrupted" what I mean is the Tag table would refer to document that have been deleted or the document could have tag that have not been inserted in the tag table.
In both of those situation it make searching a Document by tag not work correctly.
maximecaron
changed the title
Better example of keeping database integrity across containers.
PlanetaryDocs: Better example of keeping database integrity across containers.
Mar 6, 2023
When updating document, one entry in Documents container and many entry in Meta container is updated.
All those entry need to be updated atomically (either all are updated or none are updated).
Otherwise the 2 container will become out of sync if the service crash after calling HandleMetaAsync but before updating the Document container.
How can this be designed to not leave the data in the DB corrupted?
The text was updated successfully, but these errors were encountered: