fix(bigquery): revert to useInt64Timestamp for REST format options

[kurochan]

Revert BigQuery REST format options to useInt64Timestamp to avoid the
timestamp_output_format is not supported yet 400 ERRORs introduced in v1.73.0.

Related: #13788

[gemini-code-assist]

Summary of Changes

Hello @kurochan, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request provides a critical fix for the BigQuery client library, reverting a recent change that caused timestamp_output_format is not supported yet errors when interacting with the BigQuery REST API. By switching back to the useInt64Timestamp option, the library restores correct timestamp handling and ensures seamless operation for users.

Highlights

• Reverted Timestamp Format: The BigQuery REST API calls now use useInt64Timestamp instead of timestamp_output_format for timestamp formatting.
• Error Resolution: This change specifically addresses and resolves the timestamp_output_format is not supported yet 400 ERRORs that appeared in v1.73.0.
• Constant Update: The internal constant defaultTimestampWireFormat has been replaced by defaultUseInt64Timestamp to align with the new API parameter.

Changelog

• bigquery/iterator.go
  • Changed the constant defaultTimestampWireFormat (string "INT64") to defaultUseInt64Timestamp (boolean true).
  • Modified fetchTableResultPage to call FormatOptionsUseInt64Timestamp instead of FormatOptionsTimestampOutputFormat.
  • Modified fetchJobResultPage to call FormatOptionsUseInt64Timestamp instead of FormatOptionsTimestampOutputFormat.
• bigquery/job.go
  • Modified waitForQuery to call FormatOptionsUseInt64Timestamp instead of FormatOptionsTimestampOutputFormat.
• bigquery/query.go
  • Updated probeFastPath to set UseInt64Timestamp in bq.DataFormatOptions instead of TimestampOutputFormat.
• bigquery/query_test.go
  • Updated TestProbeFastPath to reflect the change from TimestampOutputFormat to UseInt64Timestamp in expected bq.DataFormatOptions for test cases.

Activity

• The pull request was created by kurochan.
• No human activity (comments, reviews, approvals) has been recorded yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request reverts the BigQuery REST format options from using timestamp_output_format back to useInt64Timestamp to fix 400 errors caused by an unsupported feature. The changes are applied consistently across iterator.go, job.go, query.go, and query_test.go, replacing the defaultTimestampWireFormat constant and its usage with defaultUseInt64Timestamp. The modifications appear correct and effectively address the bug.

[shollyman]

Thanks for this!