Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Plasma] Don't force loading the TensorFlow op on import #20556

Closed
asfimport opened this issue Dec 6, 2018 · 1 comment
Closed

[Plasma] Don't force loading the TensorFlow op on import #20556

asfimport opened this issue Dec 6, 2018 · 1 comment

Comments

@asfimport
Copy link

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).

Reporter: Philipp Moritz / @pcmoritz
Assignee: Philipp Moritz / @pcmoritz

PRs and other links:

Note: This issue was originally created as ARROW-3950. Please see the migration documentation for further details.

@asfimport
Copy link
Author

Philipp Moritz / @pcmoritz:
Issue resolved by pull request 3117
#3117

@asfimport asfimport added this to the 0.12.0 milestone Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants