[jira] [Resolved] (ARROW-3950) [Plasma] Don't force loading the TensorFlow op on import

["Philipp Moritz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARROW-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Philipp Moritz resolved ARROW-3950.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.12.0

Issue resolved by pull request 3117
[https://github.com/apache/arrow/pull/3117]

> [Plasma] Don't force loading the TensorFlow op on import
> --------------------------------------------------------
>
>                 Key: ARROW-3950
>                 URL: https://issues.apache.org/jira/browse/ARROW-3950
>             Project: Apache Arrow
>          Issue Type: Improvement
>            Reporter: Philipp Moritz
>            Assignee: Philipp Moritz
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.12.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In certain situation, users want more control over when the TensorFlow op is loaded, so we should make it optional (even if it exists). This happens in Ray for example, where we need to make sure that if multiple python workers try to compile and import the TensorFlow op in parallel, there is no race condition (e.g. one worker could try to import a half-built version of the op).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)