bigquery: drop timestamp string replacement#2647
bigquery: drop timestamp string replacement#2647stephenplusplus merged 3 commits intogoogleapis:masterfrom
Conversation
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
since https://issuetracker.google.com/issues/35905946 is fixed, bq server side now support RFC3339 format natively, hence no longer necessary to do string replacement for timestamp RFC3339 format $ node -p 'new Date().toJSON()' 2017-10-03T02:41:33.693Z $ bq query --parameter ts:TIMESTAMP:'2017-10-03T02:41:33.693Z' '#standardSQL SELECT FORMAT("%T", @ts) AS ts' Waiting on bqjob_r....... (0s) Current status: DONE +----------------------------------------+ | ts | +----------------------------------------+ | TIMESTAMP "2017-10-03 02:41:33.693+00" | +----------------------------------------+ with this change: $ node -e 'const bigquery = require("@google-cloud/bigquery")(); bigquery.query(`#standardSQL SELECT TIMESTAMP "2017-10-03T02:41:33.693Z" AS ts`) .then(([ res ]) => console.log(res))' [ { ts: { value: '2017-10-03T02:41:33.693Z' } } ] fixes googleapis#2631
5458ce1 to
baf97e5
Compare
|
CLAs look good, thanks! |
c77560e to
afd0d78
Compare
|
Thank you! |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
since https://issuetracker.google.com/issues/35905946 is fixed, bq server side
now support RFC3339 format natively, hence no longer necessary to do string
replacement for timestamp RFC3339 format
with this change:
fixes #2631