feat(genai): add batch prediction samples (2)

[jdomingr]

Description

Add new batch prediction with BigQuery sample.

Checklist

• I have followed Sample Format Guide
• Tests pass: mvn clean verify required
• Lint passes: mvn -P lint checkstyle:check required
• Static Analysis: mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
• Please merge this PR for me once it is approved

[snippet-bot]

Here is the summary of changes.

You are about to add 1 region tag.

• genai/snippets/src/main/java/genai/batchprediction/BatchPredictionWithBq.java:19, tag googlegenaisdk_batchpredict_with_bq

---

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

[gemini-code-assist]

Summary of Changes

Hello @jdomingr, 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 enhances the Generative AI samples by adding a new example for batch prediction that leverages BigQuery. The primary goal is to provide developers with a clear, runnable code sample for setting up and monitoring GenAI batch jobs where data is sourced from and results are written to BigQuery, ensuring robust integration and functionality through dedicated testing.

Highlights

• New Batch Prediction Sample: Introduced a new Java sample demonstrating how to perform batch predictions with Google Generative AI using BigQuery as both the input source and output destination.
• Batch Job Management: The sample showcases the full lifecycle of a batch prediction job, including client initialization, job creation, and polling for job status until completion.
• Integration Test Coverage: Added a comprehensive integration test using Mockito to verify the functionality of the batch prediction sample, simulating job state transitions and client interactions.

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 adds a new sample for batch prediction using BigQuery as a source and destination. The code is well-structured and includes a corresponding integration test. I have a couple of suggestions to improve the sample's usability and robustness. Specifically, I recommend making the location configurable and strengthening the polling logic to handle cases where a job state might be missing.

[msampathkumar]

@jdomingr - Please fix the file conflicts