You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Open a (reasonably large) Hyper file using the Tableau Java Hyper API
Execute a SELECT * FROM table query on the file
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.")
Java API, Linux 0.0.20027:
Calling
com.tableau.hyperapi.Result#nextRow()
when thehyperd
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:
SELECT * FROM table
query on the filekill -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
The text was updated successfully, but these errors were encountered: