You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way currently that we could make a remote schema relationship optional?
In some use cases it would be ideal that, when a query is requested including fields belonging to a remote relationship, if the remote schema is unavailable or it fails for any reason, the rest of the query still succeeds and the response includes the successful data and the error message coming form the remote server, instead of the current behavior of aborting the query and returning only the error message.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is there any way currently that we could make a remote schema relationship optional?
In some use cases it would be ideal that, when a query is requested including fields belonging to a remote relationship, if the remote schema is unavailable or it fails for any reason, the rest of the query still succeeds and the response includes the successful data and the error message coming form the remote server, instead of the current behavior of aborting the query and returning only the error message.
Beta Was this translation helpful? Give feedback.
All reactions