-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
Safe HDF5 parallel access #9641
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
Comments
You can add this as a link to the SO question in the cookbook. Doing this is quite dangerous, and the user should know exactly what they are doing. |
OK (by "dangerous" you mean if you mix the "safe" and the "standard" approach, or something else I'm missing?) |
I mean 'advanced' / 'magical', meaning that if the user doesn't understand what they are doing they get the impression that you CAN write in parallel to HDF5, which is a very-very bad idea (your serialization strategy is fine though), but this is not something pandas should enforce. In theory I agree with you, but I don't think pandas can/should really support this kind of enforcement. |
all that said am happy with a cookbook link. Something like this might be supportable in blaze |
Is something like this is worth including in pandas (although it will not work i.e. in Windows)?
If yes, I will put together a PR (also supporting Python2).
(I could also implement a platform independent alternative... but locking would not be atomic, so race conditions would be possible - although improbable)
The text was updated successfully, but these errors were encountered: