SQL retry on query plan failure, use INNER JOIN instead of EXISTS #3295
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.
At times with complex FHIR queries, the resulting SQL query is very complex and SQL server can timeout attempting to generate the query plan. We use an EXISTS clause to link References to the target type, but it reduces the burden on SQL server if we use an INNER JOIN.
This change alters the SQL query generator to use an INNER JOIN for ReferenceSearchParams.
Related issues
Addresses [issue AB#95713].
Testing
Manual testing with include .http file. Also added automated testing via member match.
FHIR Team Checklist
Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)