You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/07/12 14:05:02 UTC

[jira] [Assigned] (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:all-tabpanel ]

Todd Farmer reassigned ARROW-4003:
----------------------------------

    Assignee:     (was: Praveen Kumar)

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [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
>          Components: C++ - Gandiva, Java
>            Reporter: Praveen Kumar
>            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
(v8.20.10#820010)