[COST-4269] Fix GCP datetime format for BigQuery #470
Merged
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
maskarb
approved these changes
Nov 3, 2023
esebesto
changed the title
Codecov Report
@@ Coverage Diff @@
## main #470 +/- ##
=======================================
- Coverage 93.6% 93.5% -0.0%
=======================================
Files 60 60
Lines 4603 4603
Branches 660 660
=======================================
- Hits 4307 4306 -1
- Misses 155 156 +1
Partials 141 141 |
esebesto
changed the title
esebesto
changed the title
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.
A fix for COST-4269
the BigQuery doesn't support datetime formats with UTC offset in the form +HHMM or -HHMM.