-
Notifications
You must be signed in to change notification settings - Fork 406
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
feat(python): release GIL in the write_deltalake function #2257
feat(python): release GIL in the write_deltalake function #2257
Conversation
ACTION NEEDED delta-rs follows the Conventional Commits specification for release automation. The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification. |
Cool! If this works well I suspect that the same pattern would also be useful on other common operations (compact, vacuum, etc..) |
fc22aa9
to
0b61692
Compare
@franz101 you're missing |
Essentially all methods here correct?:
|
Looks good to me :)
…On Thu, Mar 7, 2024 at 5:22 AM franz101 ***@***.***> wrote:
Cool! If this works well I suspect that the same pattern would also be
useful on other common operations (compact, vacuum, etc..)
Essentially all methods here
<https://delta-io.github.io/delta-rs/api/delta_table/#deltalake.DeltaTable.update>
correct?:
- create
- delete
- optimize
- vacuum
- ...
—
Reply to this email directly, view it on GitHub
<#2257 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTCA6ZYPMFY7IHPXENLYXBEVZAVCNFSM6AAAAABEJ6W4NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBTGMYDAOJUGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
8888594
to
d62c17f
Compare
Description
Release GIL in deltalake.write_deltalake by wrapping it in py.allow_threads
Related Issue(s)
Documentation