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

Drop explicit check for file existence while creating GCS blobs #21105

Conversation

findinpath
Copy link
Contributor

Description

Defer the file existence check to GCS API when the blob gets actually created.

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@findinpath
Copy link
Contributor Author

Maintainer, pls test the PR with secrets

@findinpath findinpath self-assigned this Mar 15, 2024
@electrum
Copy link
Member

/test-with-secrets sha=175d8f1ddf77f417e875022e310730681bee640e

Copy link

The CI workflow run with tests that require additional secrets has been started: https://github.com/trinodb/trino/actions/runs/8302079842

Copy link
Member

@findepi findepi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Defer the file existence check to GCS API when the blob gets actually
created.
@findinpath findinpath force-pushed the findinpath/gcs-drop-explicit-file-already-exists-check branch from 175d8f1 to b3bae09 Compare March 17, 2024 08:24
@findinpath findinpath requested review from findepi and electrum March 17, 2024 08:24
@findinpath
Copy link
Contributor Author

Unrelated CI failure #18697

@wendigo wendigo merged commit a1c27da into trinodb:master Mar 17, 2024
62 checks passed
@github-actions github-actions bot added this to the 443 milestone Mar 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants