Schema composition order matters and causes query planner errors #1440
Labels
awaiting feedback
Awaiting for original poster feed back to questions and comments asked by the team.
internally-reviewed
The issue has been reviewed internally.
Hello, it seems the order in which you publish schemas to the control plane matters and will cause issues down the line.
Here is a scenario I am experiencing:
I am sorry I cannot provide full repro steps at this point as I am on mobile, I will provide a github repo later.
The error starts happening after this PR (#1092) which is released in [email protected]
In the mean time here is the error message from the router v0.107.4 up to v0.151.1. This one is specifically from 0.117.0 with minor stuff redacted:
For now a workaround seems to be to republish subgraph B's schema extending type X.
I'm sorry for not following the standard format, I will tweak this issue later.
The text was updated successfully, but these errors were encountered: