Issue 43246: Lineage query NPE while processing an UploadedFile #2325
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.
Prior to fixing Issue 41675, it was possible that a UploadedFile exp.data
imported into an assay could create a new exp.data and exp.object with
a different LSID and leave the old exp.object in the edge table. The exp.edge
table and the run ended up out of sync.
This PR finds all orphaned UploadedFile exp.object that are outputs of a run,
rebuilds the runs, and removes the orphaned exp.object rows.
Related Issues:
Related Pull Requests:
Changes: