fix: Remove unwanted excessive splitting of gcs path, so expected gcs parquet paths are returned from BigQueryRetrievalJob.to_remote_storage() #3713
Conversation
This file contains 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
crispin-ki
force-pushed
the
fix-to-remote-storage-return-value-for-big-query-retrieval-job
branch
from
fa217c3
to
4b7e490
Compare
crispin-ki
changed the title
crispin-ki
force-pushed
the
fix-to-remote-storage-return-value-for-big-query-retrieval-job
branch
from
4b7e490
to
757c79e
Compare
Signed-off-by: Crispin Logan <[email protected]>
crispin-ki
force-pushed
the
fix-to-remote-storage-return-value-for-big-query-retrieval-job
branch
from
757c79e
to
210173b
Compare
|
Closing and reopening in #3730 (done under a different GH account) |
crispin-ki
deleted the
fix-to-remote-storage-return-value-for-big-query-retrieval-job
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
See #3712
Which issue(s) this PR fixes:
Fixes #3712