[Fusion] Ignore inapplicable type refinements on abstract types #8773
+423
−4
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.
Reported here #6727 (comment)
An interface can be distributed across multiple source schemas, and each schema may implement that interface with different concrete types. The planner currently fails when you specify a type refinement for a concrete type that doesn't exist in the source schema that provides the field returning the distributed interface.
Since a source schema can only return the concrete types it actually defines, we can safely ignore inapplicable type refinements during planning.