-
Notifications
You must be signed in to change notification settings - Fork 116
Write pipe_file() data without committing a failed write #1003
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
Merged
+162
−24
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Self-review round 1 (implementation behavior) — CLEAN
Scope:
git diff 49509962cb3e81f819c59985d9f6e2ece576ffe0..9a05411b566d227ad33649e3501c3421c95731df(base = merge-base withmaster, head = published head). Covered:_write_and_close(), both callers (S3FileSystem.pipe_file()buffered path,AioS3FileSystem._pipe_file_in_transaction()),S3File._close_without_commit()and its two callers (this one and the part-limit error in_upload_chunk()), themode="create"check, fsspec'sTransactioncommit/rollback of a file closed this way, and the five new tests.Checked without findings:
commit()seesbuffer is Noneand, afterdiscard(), no parts, so it neither touches nor puts nor completes; a rollback'sdiscard()is a no-op._initiate_upload()(CreateMultipartUpload): fsspec'sflush()already setsclosed; the second close here only shuts the executor down, whichclose()used to skip for a closed file.ValueError:_close_without_commit()runs twice (in_upload_chunk()and here);discard()is then a no-op and a repeatedshutdown()is harmless for both executors (ThreadPoolExecutor.shutdown,S3AioExecutor.shutdownis a no-op).BaseException: an interrupted write no longer completes from a half-consumed buffer (the oldwithblock's final flush re-read the buffer from offset 0 after some parts were submitted).BufferError,touch()'s PutObject, upload not aborted) and pass at the head; offlinetests/pyathena/filesystem/differs from the base only by them; livetests/pyathena/filesystem/: 394 passed.Reasoned non-change:
pipe(..., compression=...)would hand a compressor wrapper to_write_and_close(), whose failure path would raiseAttributeErrorinstead of the write error.compressionis not a supportedpipeparameter (the single-request path sends it to PutObject, which rejects it), so this is not addressed.