Repository navigation
Avoid full task hydration for Jira relation lookup (JVNAUTOSCI-2737) - #606
Merged
Merged
Conversation
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
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.
Jira migration relationship repair constructed complete task responses, including text and activity lookups, when it only needed the referenced task ID. Repeated stack samples and a bounded live comparison identified this extra I/O during the estate import.
The existing external-reference resolver now supports an identity-only projection, and relationship repair selects it. The canonical source/alias selector, task-type check, organisation-first lookup and constrained legacy fallback are unchanged; other callers continue to receive full task responses.
Validation: 82 targeted tests pass, including alias/legacy-scope handling, missing/non-task records and existing import behaviour; no new Ruff findings. Both live Von and KKAT lookups returned the same IDs. Selected warm full-response reads took 0.654 and 1.667 seconds; identity reads took 0.253 and 0.639–0.728 seconds.