I don't think we should have to, but the product and customers and specific tests were coded to look for the causes() of a functionException and decide whether it should retry or not. Instead the callers should have been able to just catch the specific exceptions instead of drilling into nested causes. Maybe we can do that for Geode 2.0.
InternalFunctionInvocationTargetException should not be handed back to the caller of the function service. Those are used internally to decide whether to retry a function or not. So I can understand not wanting to send those back to a client. [ Full content available at: https://github.com/apache/geode/pull/2786 ] This message was relayed via gitbox.apache.org for [email protected]
