zentol commented on pull request #15324: URL: https://github.com/apache/flink/pull/15324#issuecomment-809989958
That should also solve the problem. I think that it would make sense, but am not sure whether it is possible while maintaining the existing class structure. ``` UnfulfillableSlotRequestException < ResourceManagerException < FlinkException NoResourceAvailableException < JobException ``` Is there a reason for why we do the exception classification via sub/parent classes, instead of interfaces? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
