Bigtable Basics
This skill provides core workflows and guidance for administering and developing
with Google Bigtable.
Core Principles
- Control Plane vs. Data Plane:
- Use
gcloud for Control Plane operations: Manage Instances,
Clusters, App Profiles, Backups and IAM. Create Tables, Logical Views,
Materialized Views and Authorized Views.
- Use
cbt for Data Plane operations: Update Tables, Column Families,
and reading/writing data.
- Performance First: Bigtable is a NoSQL database. Efficiency is tied to
Row Key design. Always warn about Full Table Scans.
- Client Selection: For production use cases, prefer Java or Go
for their superior performance and feature coverage compared to other
languages.
- Observability: When diagnosing performance or hotspotting, always
mention Key Visualizer (via Cloud Console) as the primary diagnostic
tool because it provides the most granular view of access patterns across
row keys. This should be followed by the hot-tablets tool and table stats
in gcloud CLI and
include-stats=full option under cbt read to diagnose
slow queries.
[!IMPORTANT] Safety Rule: You MUST obtain explicit user confirmation before
making non-emulator database changes. You MUST mention this safety requirement
when providing commands or instructions that modify the database structure or
data.
Quick Recipes
1. Querying Data
Use SQL for complex transforms or aggregations and key-value APIs for simpler
query patterns. Note: Use exact match, prefix (_key LIKE 'myprefix%'), or
range predicates on _key to avoid expensive unbounded scans. Recommend
explicit row ranges (_key BETWEEN 'start' AND 'end') as a more performant
alternative to prefix matches where possible.
If expensive scans (either unbounded or prefix or range queries scanning a large
range) are unavoidable due to multiple access patterns that can’t all be
accommodated in a single schema, consider one of these two options:
- If the query will be used in user facing and/or latency sensitive
applications, use continuous materialized views with keys optimized for the
additional access patterns.
- If secondary access patterns are infrequent, batch patterns like ETL, ML
model training or analytical read-only tasks, use Bigtable Data Boost
instead.
2. Manipulating Data
Use key-value APIs for insert, update, increment and delete operations. SQL API
is read-only.
3. Data Model Definition (DDL)
SQL API doesn't support DDL operations. Table creation, deletion, updates should
be made using gcloud CLI. Logical Views and Continuous Materialized Views are
defined as SQL queries but they must be created using gcloud CLI.
Reference Guides
- CLI Operations:
- infrastructure_management.md:
Provisioning instances, clusters, and table schemas.
- cli_data_access.md: Reading and writing
data via the
cbt CLI.
- Design & Discovery:
- schema_design.md: Best practices for row
keys and performance with tables and continuous materialized views.
- dataplex.md: Data catalog search for Bigtable
assets.
- Querying & Code:
- sql_guide.md: Querying structured row keys
via SQL and CLI.
- client_libraries.md: Patterns for
high-performance Go/Java/Python code.
Common Workflows
Schema Evolution (DevOps)
Prefer Terraform for production schema changes to prevent accidental
data loss.
For manual cbt changes, first check the existing state by listing the table's column families and GC policies before proposing any modifications:
cbt ls {table}
If modifications are needed, create the family or update the GC policy:
cbt createfamily {table} {family}
cbt setgcpolicy {table} {family} "maxversions=5 AND maxage=30d"
Reference
infrastructure_management.md for
full syntax.
External Resources
1---2name: bigtable-basics3metadata:4 source: https://skillmd.com/skills/google/bigtable-basics5 category: Databases6description: >-7 Assists in provisioning instances/tables, designing performant schemas, and querying data in Bigtable. Use when designing Bigtable row keys, configuring column families, writing SQL queries or client library code (Java, Go, Python) for Bigtable, or diagnosing performance/hotspotting issues. Also use when provisioning Bigtable clusters using gcloud or cbt CLIs. Don't use for generic Cloud SQL administration.8---910# Bigtable Basics1112This skill provides core workflows and guidance for administering and developing13with Google Bigtable.1415## Core Principles1617- **Control Plane vs. Data Plane:**18 - Use **`gcloud`** for Control Plane operations: Manage Instances,19 Clusters, App Profiles, Backups and IAM. Create Tables, Logical Views,20 Materialized Views and Authorized Views.21 - Use **`cbt`** for Data Plane operations: Update Tables, Column Families,22 and reading/writing data.23- **Performance First:** Bigtable is a NoSQL database. Efficiency is tied to24 Row Key design. Always warn about Full Table Scans.25- **Client Selection:** For production use cases, prefer **Java** or **Go**26 for their superior performance and feature coverage compared to other27 languages.28- **Observability:** When diagnosing performance or hotspotting, **always**29 mention **Key Visualizer** (via Cloud Console) as the primary diagnostic30 tool because it provides the most granular view of access patterns across31 row keys. This should be followed by the hot-tablets tool and table stats32 in gcloud CLI and `include-stats=full` option under `cbt read` to diagnose33 slow queries.3435> [!IMPORTANT] **Safety Rule:** You MUST obtain explicit user confirmation before36> making non-emulator database changes. You MUST mention this safety requirement37> when providing commands or instructions that modify the database structure or38> data.3940## Quick Recipes4142### 1. Querying Data4344Use SQL for complex transforms or aggregations and key-value APIs for simpler45query patterns. *Note: Use exact match, prefix (`_key LIKE 'myprefix%'`), or46range predicates on `_key` to avoid expensive unbounded scans. Recommend47explicit row ranges (`_key BETWEEN 'start' AND 'end'`) as a more performant48alternative to prefix matches where possible.*4950If expensive scans (either unbounded or prefix or range queries scanning a large51range) are unavoidable due to multiple access patterns that can’t all be52accommodated in a single schema, consider one of these two options:5354- If the query will be used in user facing and/or latency sensitive55 applications, use continuous materialized views with keys optimized for the56 additional access patterns.57- If secondary access patterns are infrequent, batch patterns like ETL, ML58 model training or analytical read-only tasks, use Bigtable Data Boost59 instead.6061### 2. Manipulating Data6263Use key-value APIs for insert, update, increment and delete operations. SQL API64is read-only.6566### 3. Data Model Definition (DDL)6768SQL API doesn't support DDL operations. Table creation, deletion, updates should69be made using gcloud CLI. Logical Views and Continuous Materialized Views are70defined as SQL queries but they must be created using gcloud CLI.7172## Reference Guides7374- **CLI Operations**:75 - [infrastructure_management.md](references/infrastructure_management.md):76 Provisioning instances, clusters, and table schemas.77 - [cli_data_access.md](references/cli_data_access.md): Reading and writing78 data via the `cbt` CLI.79- **Design & Discovery**:80 - [schema_design.md](references/schema_design.md): Best practices for row81 keys and performance with tables and continuous materialized views.82 - [dataplex.md](references/dataplex.md): Data catalog search for Bigtable83 assets.84- **Querying & Code**:85 - [sql_guide.md](references/sql_guide.md): Querying structured row keys86 via SQL and CLI.87 - [client_libraries.md](references/client_libraries.md): Patterns for88 high-performance Go/Java/Python code.8990## Common Workflows9192### Schema Evolution (DevOps)93941. **Prefer Terraform** for production schema changes to prevent accidental95 data loss.962. For manual `cbt` changes, first check the existing state by listing the table's column families and GC policies before proposing any modifications:9798 ```bash99 cbt ls {table}100 ```101102 If modifications are needed, create the family or update the GC policy:103104 ```bash105 cbt createfamily {table} {family}106 cbt setgcpolicy {table} {family} "maxversions=5 AND maxage=30d"107 ```1081093. Reference110 [infrastructure_management.md](references/infrastructure_management.md) for111 full syntax.112113## External Resources114115* [Cloud Bigtable Documentation](https://cloud.google.com/bigtable/docs)116* [Bigtable SQL Reference](https://cloud.google.com/bigtable/docs/reference/sql)117* [cbt CLI Reference](https://cloud.google.com/bigtable/docs/cbt-reference)118* [gcloud bigtable Reference](https://cloud.google.com/sdk/gcloud/reference/bigtable)