[
https://issues.apache.org/jira/browse/ARROW-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17660973#comment-17660973
]
Rok Mihevc commented on ARROW-3950:
-----------------------------------
This issue has been migrated to [issue
#20556|https://github.com/apache/arrow/issues/20556] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [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
> Components: Python
> Reporter: Philipp Moritz
> Assignee: Philipp Moritz
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.12.0
>
> Time Spent: 0.5h
> 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
(v8.20.10#820010)
