Closed guseggert closed 1 year ago
@guseggert : I put this on the 0.21 iteration. Adjust if something different should be done.
Agreed this is a small change but has a big blast radius, which is why I didn't really prioritize it before. I'm going to downgrade this to draft until we estimate costs and then figure out if we really want this.
unlikely to do anything about this anytime soon, so closing
To properly discard a transaction usually requires some external call to the backing DB, which can fail. Currently implementations just swallow any errors when discarding transactions, but this should be surfaced to the application so that it can decide the appropriate action (at the very least, log the error).
This is of course a breaking change and both datastore impls and consumers will need to be updated.