This repository has been archived by the owner on Aug 23, 2020. It is now read-only.
Fix: Don't resave the transaction itself #1671
Merged
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.
Description
While rescanning the DB we are not suppose to re-save the existing transactions themselves.
Unfortunately it seems like we were re-saving the transactions and dropping the
TAG
data itself.Type of change
How Has This Been Tested?
Currently I am rescanning a node. I will validate that Tag information is present before merging.
Complete regression test should be done seperatly in #1466
Checklist: