If the underlying transport times out, or the client goes away or network is lost, it makes sense to cancel execution and prevent further DataFetcher invocations.

There is graphql.execution.AbortExecutionException that can be raised to that effect, but requires wrapping DataFetcher's to protect their invocation. It would be useful to have a more built-in option that provides a way to cancel and stop the engine from further processing.

For some further context, see spring-graphql#450 and spring-graphql#1153.