test: Add integration tests for picosecond support

[lqiu96]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @lqiu96, 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 adds comprehensive integration tests to verify BigQuery's functionality with picosecond precision timestamps. The tests ensure that high-precision timestamps can be correctly inserted, queried, and used with named parameters, covering both valid and invalid data formats. A minor adjustment was also made to the RemoteBigQueryHelper to facilitate the custom BigQuery client configurations required for these new tests.

Highlights

• New Integration Tests: Introduced a new integration test suite (ITHighPrecisionTimestamp.java) specifically designed to validate BigQuery's support for picosecond precision timestamps.
• Enhanced Test Helper: Modified RemoteBigQueryHelper.java to allow for custom BigQueryOptions.Builder configurations, enabling more flexible setup of BigQuery clients for testing specific features like high-precision timestamps.
• Timestamp Precision Validation: The new tests cover various scenarios including querying, inserting, and using named parameters with picosecond precision timestamps, as well as validating expected failures for invalid timestamp formats and missing explicit casts in queries.

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 introduces integration tests for picosecond precision timestamp support in BigQuery. The changes involve a refactoring of RemoteBigQueryHelper to facilitate custom BigQueryOptions for testing purposes, and the addition of a new test class ITHighPrecisionTimestamp. The new tests are thorough, covering various scenarios for inserting and querying high-precision timestamps. My review includes a suggestion to remove a leftover debug statement and a couple of minor improvements in the new test file for better code style and correctness.

[jinseopkim0]

Would adding retries here help with potential flakyness, just in case insertAll takes longer than expected?

E.g. we could have a helper:

private TableResult waitForQueryResults(QueryJobConfiguration queryConfig, int expectedRows) throws InterruptedException {
    // Poll every 1 second for up to 60 seconds
    long timeoutMs = 60000;
    long startTime = System.currentTimeMillis();

    while (System.currentTimeMillis() - startTime < timeoutMs) {
        TableResult result = bigquery.query(queryConfig);
        if (result.getTotalRows() == expectedRows) {
            return result;
        }
        Thread.sleep(1000);
    }
    // Final attempt or throw error
    return bigquery.query(queryConfig);
}

Then we would have:

TableResult result = waitForQueryResults(queryJobConfiguration, 3);

[lqiu96]

I might be missing the context for this. I think the BQ client already has retry configurations set when initializing the client. IIUC, insertAll already does retries and manages request durations.