Skip to content

[spark] Support reading and writing Fluss tables through Paimon catalog - #9551

Open
Zouxxyy wants to merge 6 commits into
apache:masterfrom
Zouxxyy:xinyu/dev-paimon-fluss
Open

[spark] Support reading and writing Fluss tables through Paimon catalog#9551
Zouxxyy wants to merge 6 commits into
apache:masterfrom
Zouxxyy:xinyu/dev-paimon-fluss

Conversation

@Zouxxyy

@Zouxxyy Zouxxyy commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Purpose

Support reading and writing Fluss LakeStream tables through the Paimon Spark catalog.

  • Route Paimon FileStoreTables marked with lakestream.enabled=true to a lazily initialized Fluss Spark catalog.
  • Forward fluss.* catalog options to Fluss while keeping create, alter, and drop behavior unchanged.
  • Cover Spark 3.4 and 3.5 with routing tests and Fluss MiniCluster read/write tests.
  • Use Fluss 1.0-SNAPSHOT for the test dependencies because the stable release does not publish the required MiniCluster test jars.

Tests

  • Spark 3.4: FlussCatalogTest and FlussCatalogReadWriteITCase — 7/7 passed
  • Spark 3.5: FlussCatalogTest and FlussCatalogReadWriteITCase — 7/7 passed
  • mvn spotless:apply -Pspark3

Zouxxyy and others added 4 commits September 2, 2026 21:39
Route Paimon tables marked with lakestream.enabled to the Fluss Spark catalog and cover log and primary-key table reads and writes on Spark 3.4 and 3.5.

Co-Authored-By: Claude Code <noreply@anthropic.com>

AI-Model: gpt-5
Co-Authored-By: Codex <noreply@openai.com>
AI-Contributed/Feature: 329/329
AI-Contributed/UT: 471/471
Use the published Fluss Spark 2.12 connector test artifacts for all builds because Scala 2.13 snapshots are unavailable. Skip MiniCluster integration tests under Scala 2.13 while keeping catalog routing tests enabled.

Co-Authored-By: Claude Code <noreply@anthropic.com>

AI-Model: gpt-5
Co-Authored-By: Codex <noreply@openai.com>
AI-Contributed/Feature: 5/5
AI-Contributed/UT: 57/57
Keep Java 11 Fluss test artifacts off the Spark 3 Java 8 Surefire classpath and avoid initializing the MiniCluster below Java 11. Verify the optional connector behavior and run the Fluss read/write suites in the existing JDK 11 workflow.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Codex <noreply@openai.com>
AI-Model: gpt-5
AI-Contributed/Feature: 34/34
AI-Contributed/UT: 53/53
Keep the Java 11 Fluss test classes out of JUnit Vintage discovery after excluding their runtime dependencies from the Java 8 Surefire classpath.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Codex <noreply@openai.com>
AI-Model: gpt-5
AI-Contributed/Feature: 13/13
AI-Contributed/UT: 0/0
@Zouxxyy Zouxxyy changed the title [spark] Support reading and writing Fluss tables through Paimon catalog [spark][wip] Support reading and writing Fluss tables through Paimon catalog Sep 3, 2026
Read base Fluss LakeStream tables through Paimon while routing writes to Fluss.

Expose $rt as a read-only Fluss union view and leave $stream unsupported. Keep catalog routing in spark.catalog and table adapters in spark.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Codex <noreply@openai.com>
AI-Model: gpt-5
AI-Contributed/Feature: 279/279
AI-Contributed/UT: 196/196
@Zouxxyy Zouxxyy changed the title [spark][wip] Support reading and writing Fluss tables through Paimon catalog [spark] Support reading and writing Fluss tables through Paimon catalog Sep 3, 2026
Document the loader interfaces required by Checkstyle.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Codex <noreply@openai.com>
AI-Model: gpt-5
AI-Contributed/Feature: 2/2
AI-Contributed/UT: 0/0
@JingsongLi

Copy link
Copy Markdown
Contributor

cc @luoyuxia

@JingsongLi

Copy link
Copy Markdown
Contributor

We should provide standard abstractions to allow Fluss to be integrated via plugins, rather than hardcoding it.

@luoyuxia

luoyuxia commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

I'll push forward the PIP-39: Enable In-Place Upgrade of Existing Paimon Tables for Sub-Second Latency via Fluss to propose the abstraction/change for both flink and spark

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants