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
We have the hive gateway set up in the supergraph configuration reading from a static supergraph.graphql file. It does not appear like there's an option currently to do this, looking through the gateway server code, it looks like the requestTimeout option would need to be passed in here.
Our current workaround is to set the timeout on the graphql datasources directly on the supergraph schema. However, ideally we'd like to be able to set an overall request timeout on the server itself rather than relying on the fetch resolution timeouts to subgraphs.
The text was updated successfully, but these errors were encountered:
Yes, that would be great, thank you! In the mean time, we were able to figure out how to use transportEntries to configure a timeout for each subgraph at runtime. If there was some additional documentation on that option, I think it would have saved us some time.
We have the hive gateway set up in the supergraph configuration reading from a static
supergraph.graphql
file. It does not appear like there's an option currently to do this, looking through the gateway server code, it looks like therequestTimeout
option would need to be passed in here.Our current workaround is to set the timeout on the graphql datasources directly on the supergraph schema. However, ideally we'd like to be able to set an overall request timeout on the server itself rather than relying on the fetch resolution timeouts to subgraphs.
The text was updated successfully, but these errors were encountered: