apache/seatunnel

[Feature][Connector] Add Google Bigtable Connector

Open

#10847 opened on May 6, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (6,897 stars) (1,432 forks)batch import
featuregood first issuehelp wanted

Description

Search before asking

  • I had searched in the feature and found no similar feature requirement.

Description

Google Bigtable is Google Cloud's fully managed wide-column NoSQL database for low-latency and high-throughput workloads. It is commonly used for time-series, IoT telemetry, user profile, recommendation, and operational analytics scenarios.

Currently, SeaTunnel does not provide a native Google Bigtable connector. This prevents users from building pipelines between Bigtable and other systems in the SeaTunnel ecosystem without writing custom integration code.

I would like to propose adding a dedicated Google Bigtable connector family for SeaTunnel Connector-V2. The implementation can be delivered incrementally, but the overall goal should cover:

  1. Google Bigtable Source connector
  2. Google Bigtable Sink connector

Suggested capabilities:

  • Native Google Cloud Bigtable Java client based implementation instead of generic workarounds
  • Batch read and write support
  • Schema mapping between SeaTunnelRow and Bigtable row key / column family / qualifier model
  • Configurable row key strategy
  • Support for multiple column families
  • Good handling for sparse columns and versioned cells
  • Authentication through service account credentials and application default credentials

If the full connector family is too large for one contribution, it is also fine to start from the Sink side first and extend to Source in follow-up work.

Usage Scenario

Typical scenarios include:

  • Writing real-time or batch processed data from Kafka / CDC / JDBC sources into Bigtable for online serving
  • Exporting Bigtable data into data lake, warehouse, or search systems through SeaTunnel
  • Synchronizing operational data between Bigtable and other cloud or on-prem systems
  • Using SeaTunnel as a standardized integration layer for GCP-native architectures

Related issues

  • No dedicated Google Bigtable feature issue was found when checking current apache/seatunnel issues and pull requests on 2026-05-06.
  • There are related GCP requests for GCS and BigQuery, but no current tracker specifically covering Google Bigtable.

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Tech stack
java
Domain
databackendcloud
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaSeaTunnel connector APIGoogle BigtableGCP authentication
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Start by reviewing the existing Google Cloud connectors in the repository, specifically the BigQuery connector, to understand the connector structure and required interfaces. Then study the Google Cloud Bigtable Java client library. The issue suggests starting with the Sink connector, so focus on that. Look at the issue comments for any clarifications.