You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Jacques Nadeau (JIRA)" <ji...@apache.org> on 2018/12/12 09:07:00 UTC
[jira] [Comment Edited] (ARROW-4003) [Gandiva][Java] Safeguard jvm
before loading the gandiva library
[ https://issues.apache.org/jira/browse/ARROW-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718648#comment-16718648 ]
Jacques Nadeau edited comment on ARROW-4003 at 12/12/18 9:06 AM:
-----------------------------------------------------------------
This seems like overkill. I'm not aware of any other native library packaged for Java that does this. Why do you think is necessary?
was (Author: jnadeau):
This seems like overkill. I'm not aware of any other native library packaged for Java stuff that does this. Why do you think is necessary?
> [Gandiva][Java] Safeguard jvm before loading the gandiva library
> ----------------------------------------------------------------
>
> Key: ARROW-4003
> URL: https://issues.apache.org/jira/browse/ARROW-4003
> Project: Apache Arrow
> Issue Type: Task
> Reporter: Praveen Kumar Desabandu
> Assignee: Praveen Kumar Desabandu
> Priority: Major
>
> Today we load the gandiva library always when trying to use the jni bridge, but we have run into issues causing the jvm to crash in untested paths.
> Proposal is to do load the library in a separate process first and if it works only then load in the current process.
> This would be done only once at startup/first load.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)