chore: Fix short query tests

[lqiu96]

Fixes: #4105 and #4106

[gemini-code-assist]

Summary of Changes

Hello, 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 addresses issues where short BigQuery queries, expected to be stateless, might still result in a job being created, leading to inconsistent JobId and QueryId behavior in TableResult. It introduces a JobCreationReason enum to provide explicit context for why a job was created, enhancing the clarity and debuggability of query execution. The changes also update relevant integration tests to correctly validate this new behavior and ensure robust handling of query results.

Highlights

• New Enum for Job Creation Reason: Introduced a new JobCreationReason enum to categorize why a BigQuery job was created, providing explicit context for query execution.
• Integration of Job Creation Reason: Integrated the JobCreationReason into TableResult and BigQueryImpl to store and retrieve the reason for job creation when processing query responses.
• Updated Query Integration Tests: Modified integration tests (ITBigQueryTest) to accurately assert the JobCreationReason and the relationship between JobId and QueryId for short queries, addressing previous inconsistencies.
• OpenTelemetry SDK Initialization Fix: Corrected the OpenTelemetry SDK initialization in integration tests by changing buildAndRegisterGlobal() to build().

Changelog

• google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/BigQueryImpl.java
  • Added logic to set JobCreationReason when building TableResult from query responses.
• google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/JobCreationReason.java
  • Added a new enum JobCreationReason to represent why a BigQuery job was created.
• google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/TableResult.java
  • Added JobCreationReason field and its builder/getter methods.
• google-cloud-bigquery/src/test/java/com/google/cloud/bigquery/it/ITBigQueryTest.java
  • Updated assertions for testTableResultJobIdAndQueryId and testQueryWithTimeout to check JobCreationReason and JobId/QueryId consistency.
  • Changed OpenTelemetry SDK initialization to build() instead of buildAndRegisterGlobal().

Activity

• No specific activity (comments, reviews, progress) has been provided for this pull request 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

The pull request introduces the JobCreationReason enum and integrates it into the BigQueryImpl and TableResult classes. This enhancement allows for better tracking of why a BigQuery job was created, especially in scenarios involving JOB_CREATION_OPTIONAL mode. The integration appears sound, and the updated integration tests (ITBigQueryTest.java) correctly reflect and validate the new functionality, including handling cases where simple queries might still result in job creation with an OTHER reason. The changes are well-contained and address the linked issues effectively.

[jinseopkim0]

This would be thrown if a new enum is added in the backend, right? Would it make sense to return an enum like UNKNOWN instead of throwing an exception?

[lqiu96]

Ah good point. I removed the exception and used KNOWN AS the default if the mapping doesn't exist.

AIPs suggest that enums shouldn't be changing too much in the future so I don't expect UNKNOWN to be used at all. I think it would be better than having client-side validation if the off chance that there is. Updated!