Skip to content

BIGQUERY.md

Latest commit

 

History

History
37 lines (24 loc) · 2.4 KB

BIGQUERY.md

File metadata and controls

37 lines (24 loc) · 2.4 KB

Setup

Required Gemini CLI Version

To install this extension, the Gemini CLI version must be v0.6.0 or above. The version can be found by running: gemini --version.

BigQuery Skills (Data Plane: Connecting and Querying)

This section covers connecting to BigQuery.

  1. Extension Configuration: This extension requires several settings (e.g., Project ID, Location). These values are gathered via prompts when you first install or link the extension:
  • BIGQUERY_PROJECT: The GCP project ID.
  • BIGQUERY_LOCATION: (Optional) Location of the BigQuery resources.

If you need to update any of these values later, use the gemini extensions config bigquery-data-analytics command.

  1. Handle Missing Variables: If a command fails with an error message containing a placeholder like ${BIGQUERY_PROJECT}, it signifies a missing environment variable. Inform the user which variable is missing and instruct them to set it.

  2. Handle Permission Errors:

  • For operations that execute queries and view metadata, the user needs the BigQuery User (roles/bigquery.user) and BigQuery Metadata Viewer (roles/bigquery.metadataViewer) role.
  • For operations that create, or modify datasets and tables, the user needs the BigQuery Data Editor (roles/bigquery.dataEditor) role.
  • If an operation fails due to permissions, identify the type of operation and recommend the appropriate role. You can provide these links for assistance:
  • Granting Roles: https://cloud.google.com/iam/docs/grant-role-console
  • BigQuery Permissions: https://cloud.google.com/iam/docs/roles-permissions/bigquery

2. BigQuery AI/ML Skills

These skills leverage BigQuery's built-in AI functions (AI.*) for tasks like text generation, classification, and semantic search.

Important: Standard SQL-based AI.* functions (executed via execute_sql()) are preferred over dedicated BigQuery tools for tasks like Forecasting and Anomaly Detection.

  1. Prerequisites:
  • Ensure your BigQuery project has the Vertex AI API enabled.
  • A Cloud Resource Connection must be established in BigQuery to use AI.* functions.
  1. Handle Permission Errors:
  • The service account associated with the BigQuery connection requires the Vertex AI User (roles/aiplatform.user) and the BigQuery Connection User (roles/bigquery.connectionUser) role.