← Back to all sparks
A

Apache SeaTunnel

ANALYTICS
Velocity0.0

High-performance distributed data integration platform

SeaTunnel 3.0 ends a six-month gap with 927 PRs and 30 new connectors.

data integrationconnectorscdcapache projectetl
◆Current state
Apache SeaTunnel shipped 3.0.0 on 30 September, its first release since March: 927 merged PRs, 30 new connectors (BigQuery, Salesforce, Google and TikTok Ads, Stripe, Shopify, Mem0, Deep Lake and more), a Python transform, PostgreSQL CDC add-column schema evolution and connectivity dry-runs for S3 and Kafka sources. The prior 2.3.13 release made large files splittable across readers.
◆Where it's heading
The connector catalogue is moving beyond databases and file stores into SaaS APIs and ad platforms, plus vector and memory stores. Schema evolution in CDC sources keeps widening, one database at a time, and the major version resets expectations after a lengthening release interval.
◆Prediction
Expect 3.0.x patch releases fixing the new connectors, given how much landed in one version.

◆Recent moves

  1. 1mo ago

    SeaTunnel 3.0 adds 30 connectors and a Python transform

    3.0.0 bundles 927 PRs and 30 connectors, reaching SaaS and ad platforms (Salesforce, Google Ads, Stripe, Shopify) and AI stores (Mem0, Deep Lake), plus a Python transform. The scale would merit a spark, but the release is over a month old and reached SparkPulse late.

    View source ↗
  2. 7mo ago

    Large files split for parallel read; CDC schema evolution on Flink

    ⚡ SPARK

    The release that lifts SeaTunnel past a structural limit — one file no longer means one reader — while adding schema evolution for CDC sources on Flink. It is also the last release the project has published, which makes it both the high point and the start of the current quiet stretch.

    View source ↗
  3. 1y ago

    Documentation sweep with JDBC and Iceberg updates

    A release weighted toward documentation — broken links, DynamoDB parameter corrections, a Zeta tuning guide, and Iceberg docs updated for S3 Tables REST catalogues. Useful, but it is the connector docs catching up with connectors that already shipped.

    View source ↗
  4. 1y ago

    Chinese connector documentation added in bulk

    Almost entirely Chinese translations of existing connector documentation — MySQL CDC, MongoDB CDC, HiveJdbc, Jira and others. It reflects where the contributor base is, and changes nothing functional.

    View source ↗
  5. 1y ago

    Connector option handling normalized across the catalogue

    A sweep through connector configuration — InfluxDB, HTTP, IoTDB, email, Web3j and local file options all reworked, with one change reverted in the same release. Tidying config surfaces across dozens of connectors is unglamorous and exactly what a catalogue this size needs.

    View source ↗
  6. 1y ago

    Type conversion and connector bug fixes

    A bug fix rollup: Avro short-to-int conversion, a null pointer when source fields are fewer than Hive target fields, MongoDB BSON conversion and a Hadoop Kerberos failure. Individually narrow, collectively the long tail of a wide connector surface.

    View source ↗