Skip to content

Conversation

@keshavdandeva
Copy link

b/474642014

Add README.md for google-cloud-bigquery-jdbc

@keshavdandeva keshavdandeva requested a review from a team as a code owner January 20, 2026 15:12
@product-auto-label product-auto-label bot added size: l Pull request size is large. api: bigquery Issues related to the googleapis/java-bigquery API. labels Jan 20, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @keshavdandeva, I'm Gemini Code Assist1! 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 introduces a new README.md file for the google-cloud-bigquery-jdbc module. This addition significantly enhances the project's documentation, providing a central and comprehensive resource for users and contributors to quickly understand how to get started, develop, test, and deploy the BigQuery JDBC client. The new README aims to improve developer experience by consolidating crucial information in one accessible location.

Highlights

  • New README.md Added: A comprehensive README.md file has been added to the google-cloud-bigquery-jdbc module, providing essential documentation for developers and users.
  • Quickstart and Installation Guide: The new README includes detailed instructions for quick setup using Maven, Gradle, and SBT, along with prerequisites and installation steps for the BigQuery JDBC client.
  • Developer and Testing Information: A dedicated developer guide covers prerequisites, setup, running unit and integration tests (including Dockerized environments), packaging options (thin and full jars), custom query testing, night builds, performance tests, and code coverage.
  • Comprehensive Operational Details: Important sections on authentication, authorization, supported Java versions, troubleshooting, versioning, contributing guidelines, licensing, and CI status have been included to provide a complete overview of the project.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

Copy link
Contributor

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

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 introduces the README.md file for the google-cloud-bigquery-jdbc project. The README covers essential aspects such as quickstart instructions, authentication, authorization, a developer guide, packaging details, and supported Java versions. While the content is comprehensive, there are several areas that require attention to improve accuracy, clarity, and maintainability. These include version inconsistencies in dependency declarations, several typos, an incorrect example command for integration tests, and the presence of internal Google URLs that should not be in a public-facing document. Addressing these points will significantly enhance the quality and usefulness of the documentation.

Comment on lines +158 to +159

Nightly Integration Tests include a step to build a full and thin jars and upload them to [Google Storage](https://pantheon.corp.google.com/storage/browser/bq_devtools_release_private/drivers/jdbc;tab=objects?inv=1&invt=Ab4E6g&project=bigquery-devtools-drivers&prefix=&forceOnObjectsSortingFiltering=false).
Copy link
Contributor

Choose a reason for hiding this comment

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

critical

This URL points to an internal Google Storage location (pantheon.corp.google.com). This should not be present in a public README. Please remove this link and the associated descriptive text, or replace it with a public-facing alternative if one exists.

Suggested change
Nightly Integration Tests include a step to build a full and thin jars and upload them to [Google Storage](https://pantheon.corp.google.com/storage/browser/bq_devtools_release_private/drivers/jdbc;tab=objects?inv=1&invt=Ab4E6g&project=bigquery-devtools-drivers&prefix=&forceOnObjectsSortingFiltering=false).
Nightly Integration Tests include a step to build a full and thin jars and upload them to Google Storage.

Comment on lines +170 to +171
[Cloud Build Pipeline](https://pantheon.corp.google.com/cloud-build/triggers;region=us-east1/edit/125214da-8603-449d-8336-b6dba7196bb4?project=bigquery-devtools-drivers)
is uploading latest full jar to the internal location for perf tests once a week, at the moment scheduled to do this Sunday night.
Copy link
Contributor

Choose a reason for hiding this comment

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

critical

This URL points to an internal Cloud Build Pipeline (pantheon.corp.google.com). This should not be present in a public README. Please remove this link and the associated descriptive text, or replace it with a public-facing alternative if one exists.

Suggested change
[Cloud Build Pipeline](https://pantheon.corp.google.com/cloud-build/triggers;region=us-east1/edit/125214da-8603-449d-8336-b6dba7196bb4?project=bigquery-devtools-drivers)
is uploading latest full jar to the internal location for perf tests once a week, at the moment scheduled to do this Sunday night.
Performance tests are uploading latest full jar to the internal location for perf tests once a week, at the moment scheduled to do this Sunday night.

If you are using Gradle without BOM, add this to your dependencies:

```Groovy
implementation 'com.google.cloud:google-cloud-bigquery-jdbc:0.1.0'
Copy link
Contributor

Choose a reason for hiding this comment

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

high

Similar to the Maven dependency, the Gradle dependency version (0.1.0) should align with the pom.xml's 0.1.0-SNAPSHOT or the intended release version.

Suggested change
implementation 'com.google.cloud:google-cloud-bigquery-jdbc:0.1.0'
implementation 'com.google.cloud:google-cloud-bigquery-jdbc:0.1.0-SNAPSHOT'

If you are using SBT, add this to your dependencies:

```Scala
libraryDependencies += "com.google.cloud" % "google-cloud-bigquery-jdbc" % "0.1.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The SBT dependency version (0.1.0) should also be consistent with the pom.xml's 0.1.0-SNAPSHOT or the intended release version.

Suggested change
libraryDependencies += "com.google.cloud" % "google-cloud-bigquery-jdbc" % "0.1.0"
libraryDependencies += "com.google.cloud" % "google-cloud-bigquery-jdbc" % "0.1.0-SNAPSHOT"

<dependency>
<groupId>com.google.cloud</groupId>
<artifactId>google-cloud-bigquery-jdbc</artifactId>
<version>0.1.0</version>
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The version specified here (0.1.0) is inconsistent with the pom.xml which shows 0.1.0-SNAPSHOT. Please ensure the version in the README accurately reflects the current or intended release version. If this is a development version, 0.1.0-SNAPSHOT should be used for consistency.

Suggested change
<version>0.1.0</version>
<version>0.1.0-SNAPSHOT</version>

make docker-integration-test
```

Please note that running unit of integration tests within docker doesn't leverage maven cache because it is not persisted.
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The phrasing "unit of integration tests" is a bit awkward. Consider changing it to "unit or integration tests" for better readability.

Suggested change
Please note that running unit of integration tests within docker doesn't leverage maven cache because it is not persisted.
Please note that running unit or integration tests within docker doesn't leverage maven cache because it is not persisted.


`make integration-test`

Run specific unitintegration test
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

There is a typo here; 'unitintegration' should be 'integration'.

Suggested change
Run specific unitintegration test
Run specific integration test

Comment on lines +291 to +292
[kokoro-badge-image-1]: http://storage.googleapis.com/cloud-devrel-public/java/badges/java-bigquery-jdbc/java7.svg
[kokoro-badge-link-1]: http://storage.googleapis.com/cloud-devrel-public/java/badges/java-bigquery-jdbc/java7.html
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

These link definitions for kokoro-badge-image-1 and kokoro-badge-link-1 are not used anywhere in the document. Please remove unused link definitions to keep the README clean and maintainable.

Comment on lines +317 to +318
[libraries-bom]: https://github.com/GoogleCloudPlatform/cloud-opensource-java/wiki/The-Google-Cloud-Platform-Libraries-BOM
[shell_img]: https://gstatic.com/cloudssh/images/open-btn.png
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

These link definitions for libraries-bom and shell_img are not used in this README. Please remove unused link definitions to keep the README clean and maintainable.

[cloudlibs]: https://cloud.google.com/apis/docs/client-libraries-explained
[apilibs]: https://cloud.google.com/apis/docs/client-libraries-explained#google_api_client_libraries
[oracle]: https://www.oracle.com/java/technologies/java-se-support-roadmap.html
[g-c-j]: http://github.com/googleapis/google-cloud-java No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The link definition for g-c-j is not used in this README. Please remove unused link definitions to keep the README clean and maintainable.

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

Labels

api: bigquery Issues related to the googleapis/java-bigquery API. size: l Pull request size is large.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant