Skip to main content

Ecosystem

Use Paimon tables across ingestion pipelines, SQL engines, and lakehouse management tools. Start with an integration below, then follow Connecting Engines to configure catalog discovery and storage access.

Flink and Spark write Paimon tables; SQL engines query the shared tables, while Amoro provides table management.

Choose an Integration​

What you want to doStart here
Ingest CDC events or build a streaming pipelineFlink Quick Start, CDC Ingestion
Run batch transformations or Spark SQLSpark Quick Start
Process streams with Spark micro-batchesSpark Structured Streaming
Query Paimon from an OLAP engineStarRocks, Doris
Query or write tables with distributed SQLTrino
Access tables from HiveHive
Inspect tables in a lakehouse management serviceAmoro

Compatibility Matrix​

For bundled connectors, match the engine version to the connector artifact for your Paimon release. The Flink, Spark, and Hive versions below describe connector modules in this branch; artifact availability depends on the release. Externally maintained integrations have their own release cycle, embedded Paimon version, and feature limits.

IntegrationVersion selectionAccess to Paimon tables
Flink1.16–1.20 and 2.0–2.2Batch and streaming reads/writes; DDL and row changes have version-specific requirements.
Spark3.2–3.5, 4.0, and 4.1; match the Scala binary versionBatch reads/writes, DDL, and row changes; streaming requires Spark 3.3+.
Hive2.1, 2.2, 2.3, 3.1, and 2.1-cdh-6.3Batch reads, table creation, and INSERT INTO; writes require MapReduce.
TrinoMatch the independently released Paimon connector to TrinoBatch reads; supported connectors also provide DDL, inserts, and time travel. See the guide's table-layout limits.
PrestoFollow the separate connector's version requirementsSee the connector repository for installation and supported operations.
StarRocksPaimon catalogs available from 3.1Query existing tables through an external catalog; check the engine release for individual features.
DorisSelect a release with the required catalog and reader featuresQuery existing tables through an external catalog; REST catalog access requires Doris 3.1+.

A connector's ability to read a table also depends on its data types, file format, merge engine, and enabled features, such as deletion vectors. Check the relevant engine guide before enabling a new table feature in a warehouse shared by several engines.

Streaming Engines​

Use Flink for continuous ingestion, change processing, and lookup joins. Use Spark Structured Streaming for micro-batch pipelines. Configure the table's changelog producer for the changes that downstream readers need.

Batch Engines​

Use Spark SQL or Flink batch SQL to read a snapshot and run transformations. Consult the write guides for Spark and Flink before using overwrite, DELETE, UPDATE, or MERGE INTO: SQL support and table requirements differ by engine and version.

OLAP Engines​

StarRocks and Doris query Paimon through their own external catalogs. Trino and Presto use separately distributed connectors. Configure access to both the catalog and the underlying files, and choose the table read mode for your freshness requirements.

Download​

Use the engine downloads for Paimon artifacts and each integration guide for installation. For Trino and Presto, use the connector project's release instructions; its version does not necessarily match this documentation's Paimon version.