fix: interpret Integer and Float values for TIMESTAMP as microseconds #2175
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
product-auto-label
bot
added
size: m
agrawal-siddharth
force-pushed
the
fixTimestamp
branch
from
2054115
to
5e4b3d4
Compare
Neenu1995
added
kokoro:force-run
gcf-owl-bot
bot
removed
the
owlbot:run
yoshi-kokoro
removed
kokoro:force-run
agrawal-siddharth
force-pushed
the
fixTimestamp
branch
from
af01fa6
to
7514155
Compare
GaoleMeng
approved these changes
Jul 6, 2023
Neenu1995
added
the
owlbot:run
gcf-owl-bot
bot
removed
the
owlbot:run
Neenu1995
approved these changes
Jul 10, 2023
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.
Fixes internal bug 288224075.
Make handling of Integer and Float (as string) consistent with that of Long.