Remove timezone on time format as it violated with BigQuery timeformat #46
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
|
Format should be configurable. |
|
Thanks @repeatedly, I will fix it soon |
|
By the way there is a BigQuery specific fluentd plugin that I have been using for a while now that seems to work very well. |
|
Hi, any updates regarding this PR ? I'm currently facing a timestamp issue which should be fixed by this change: The comparison fails with the update_column fails on MySQL because of the timezone, as seen here: If I remove the timezone from the state file manually, it works fine (although it re-writes it incorrectly a second later) |
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.
Hi @repeatedly
This PR aim to fix the error when streaming to BigQuery, related to this PR #45
<Google::Apis::BigqueryV2::ErrorProto:0x007fd4aa24d8b8 @debug_info=\“generic::invalid_argument: Could not parse ‘2017-03-13 07:21:09.177000+0000’ as a timestamp. Required format is YYYY-MM-DD HH:MM[:SS[.SSSSSS]]\“, @location=\“created_at\“, @message=\“Could not parse ‘2017-03-13 07:21:09.177000+0000’ as a timestamp. Required format is YYYY-MM-DD HH:MM[:SS[.SSSSSS]]\“, @reason=\“invalid\“>], @index=1>]”