rocketraman08/14/2022, 4:11 PM
) from my db driver. While I continue to investigate the root cause of this, I'd like to add a workaround with some retry logic. Since the underlying exception could occur pretty much anywhere, I'm thinking having the logic at the graphql-kotlin layer makes sense, if it is possible. What would the right way to do this? Would an interceptor work for this case?
IOException: Broken pipe
is invoked for the entire message. Would be nice to be able to retry the fetch for just the field that failed, but I'd settle for retrying the entire thing.
Dariusz Kuc08/14/2022, 11:01 PM
rocketraman08/15/2022, 12:42 AM
Arnab08/16/2022, 11:01 AM