Skip to content

fix(bigquery): propagate DataFormatOptions to listTableData/getQueryResults and FieldValue - #14651

Draft
lqiu96 wants to merge 1 commit into
mainfrom
perf/bq-t1-04-timestamp-parsing-and-option
Draft

lqiu96 wants to merge 1 commit into
mainfrom
perf/bq-t1-04-timestamp-parsing-and-option

Conversation

@lqiu96

@lqiu96 lqiu96 commented Oct 13, 2026

Copy link
Copy Markdown
Member

No description provided.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the BigQuery client to propagate the full DataFormatOptions (including timestamp output format) instead of just a boolean useInt64Timestamps flag across BigQueryImpl, BigQueryOptions, FieldValue, FieldValueList, and HttpBigQueryRpc. Additionally, it optimizes timestamp parsing in FieldValue.getTimestampValue() by using Long.parseLong instead of allocating a BigInteger when useInt64Timestamps is enabled. Unit tests have been updated and a new test has been added to verify the propagation of these options to RPC requests. There are no review comments to address, and I have no further feedback to provide.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant