Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document issue for TIMESTAMP in "Introduction to the BigQuery Storage Write API" #417

Open
huilingwei opened this issue Feb 20, 2024 · 0 comments
Assignees
Labels
api: bigquerystorage Issues related to the googleapis/nodejs-bigquery-storage API. priority: p2 Moderately-important priority. Fix may not be included in next release.

Comments

@huilingwei
Copy link

In document "Introduction to the BigQuery Storage Write API", description for TIMESTAMP in Chinese is inconsistent with English.

In Chinese document the unit of timestamp is 毫秒, while in English document it is microseconds, microseconds should be 微秒。

Doc URL: https://cloud.google.com/bigquery/docs/write-api

@huilingwei huilingwei added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Feb 20, 2024
@product-auto-label product-auto-label bot added the api: bigquerystorage Issues related to the googleapis/nodejs-bigquery-storage API. label Feb 20, 2024
@alvarowolfx alvarowolfx self-assigned this Feb 20, 2024
@alvarowolfx alvarowolfx added api: docs Issues related to the Docs API API. and removed type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Feb 20, 2024
@product-auto-label product-auto-label bot removed the api: docs Issues related to the Docs API API. label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquerystorage Issues related to the googleapis/nodejs-bigquery-storage API. priority: p2 Moderately-important priority. Fix may not be included in next release.
Projects
None yet
Development

No branches or pull requests

2 participants