GitHub user beryllw edited a comment on the discussion: Apache Fluss Roadmap 2026
# fluss-rust & Fluss Gateway 2026 Roadmap > North Star: make fluss-rust a first-class analytical query surface — a > Rust-native SQL/DataFrame path over Fluss, reading the lake tier at scale — > with Fluss Gateway as the HTTP/SQL frontend built on top. ## 🦀 Theme 1 — fluss-rust Core consolidation and the Rust-native analytical read path. ### Pillar 1.1 — Core Consolidation - [ ] FIP-40: consolidate apache/fluss-rust into apache/fluss (PR #3401) - [ ] Workspace-wide Arrow / DataFusion version pinning - [ ] Split into scoped crates: core, lake, DataFusion adapter, gateway ### Pillar 1.2 — DataFusion Integration Adapter A standalone adapter over the Rust core, not a bundled engine. - [ ] TableProvider + Catalog on top of the existing client - [ ] Pushdown mapping onto existing access paths (lookup / prefix / bounded scan / log scan) ### Pillar 1.3 — Lake + Log Union Read (Paimon-first) Present a lake-enabled table as one logical table, in an isolated fluss-lake submodule. - [ ] Bounded batch union read (Lake abstraction to keep Iceberg / Lance slot-in friendly, Paimon first, streaming later) ### Pillar 1.4 — Server-Side Filter Pushdown (optional in 0.3.0) - [ ] Close the gap with the Java client on value-predicate pushdown ## 🌐 Theme 2 — Fluss Gateway (post-0.3.0, separate module) > Depends on fluss-rust, decoupled from the 0.3.0 release train. Delivered as > three FIPs. - [ ] [FIP-32: Multiprotocol Query Gateway for Apache Fluss](https://cwiki.apache.org/confluence/spaces/FLUSS/pages/406622520/FIP-32+Multiprotocol+Query+Gateway+for+Apache+Fluss) - [ ] FIP: Fluss REST Gateway — plain read / write / metadata REST API, independent of Pillars 1.2–1.3 - [ ] FIP: Fluss SQL Gateway — SQL surface on top of Pillars 1.2–1.3 - [ ] FIP: Gateway Auth & Authorization — user ↔ gateway authN, gateway ↔ server identity model, ACL enforcement location GitHub link: https://github.com/apache/fluss/discussions/2342#discussioncomment-17518576 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
