SIGSEGV in native code of Java HyperAPI library after hyperd was killed unexpectedly

[jannik-loescher-knime]

Java API, Linux 0.0.20027, 0.0.20746:

Calling com.tableau.hyperapi.Result#nextRow() when the hyperd process is not available anymore causes a segmentation fault SIGSEGV in native code, crashing the whole JVM.
We run the JVM+hyperd in an containerized environment and processes consuming too much memory are getting killed to enforce memory bounds.

How to reproduce:

1. Open a (reasonably large) Hyper file using the Tableau Java Hyper API
2. Execute a SELECT * FROM table query on the file
3. While the query is being read, kill the hyperd process forcefully: kill -9 $(pgrep hyperd)

Expected behavior:
A catchable Java Exception is thrown, similarly to com.tableau.hyperapi.Inserter#execute() ("Failed to insert into table […]:The Hyper server closed the connection unexpectedly.")

Crash report: hs_err_pid1794671.log

[koettert]

Hello everyone and a happy new year. Is there any update on this problem?
Thanks
Tobias

[marcelkost]

Hey everyone - the problem should be fixed in January 2025 release of Hyper API. Please let us know if you still encounter problems.

[koettert]

Hello @marcelkost this is great news. We will try the fix latest beginning of next week and report back. Thanks a lot for the quick release.

[koettert]

The fix works. Thanks a lot.