[ARROW-16329] [Java][C++] Keep more context when marshalling errors through JNI

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 9.0.0
• Component/s: C++, Java
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/31713
• Assignee: Hongze Zhang
• Reporter: Antoine Pitrou
• Created: 26/Apr/22 07:44
• Updated: 11/Jan/23 11:43
• Resolved: 06/Jul/22 11:56

Description

When errors are propagated through the JNI barrier, two mechanisms are involved:

• the Status CheckException(JNIEnv* env) function for Java-to-C++ error translation
• the JniAssertOkOrThrow(arrow::Status status) and T JniGetOrThrow(arrow::Result<T> result) functions for C++-to-Java error translation

Currently, both mechanisms lose most context about the original error, such as its type and any additional state, such as the optional StatusDetail in C++ or any properties in Java (which I'm sure exist on some exception classes).

We should improve these mechanisms to retain as much context as possible. For example, in a hypothetical Java-to-C++-to-Java error propagation scenario, the original Java exception from inner code should ideally be re-thrown in the outer Java context (we already support this in Python btw).

Issue Links

• links to: GitHub Pull Request #13246