GitHub user MehulBatra added a comment to the discussion: Apache Fluss Roadmap 2026
# Fluss x Iceberg 2026 Roadmap **Pillar 1: Format & Schema Evolution** Modernizing Iceberg integration with V3 capabilities and seamless schema management. - [ ] Iceberg V3 Support: Deletion Vectors, Puffin files, Row-Level Lineage, Variant datatype, timestamp_ns/timestamptz_ns - [ ] Schema Evolution: Add column, alter column types, rename column with automatic Fluss → Iceberg sync - [ ] Schema Cleanup: Remove Fluss system columns (__offset, __bucket, __timestamp) from Iceberg tables **Pillar 2: Catalog Ecosystem** Expanding catalog support and documentation. - [ ] Catalog Integration: AWS Glue, Databricks Unity, Polaris catalog support - [ ] Documentation: All catalogs support Iceberg REST protocol (Fluss already powers Iceberg REST protocol) **Pillar 3: Performance Optimization** Accelerating write/read paths and adaptive tiering. - [ ] Deletion Vectors: Full-path integration (write + read) for 10-100x faster deletes - [ ] Adaptive Tiering: File sizing during tiering based on workload patterns **Pillar 4: Multi-Engine Ecosystem Integration** Enabling unified hot + cold queries across compute engines. - [ ] Batch Union Read: Support across for unified hot + cold queries - Spark, - Trino, - StarRocks **Pillar 5: In-Place Lakehouse Integration** Define Fluss tables on existing Iceberg data without migration. - [ ] Use Iceberg as historical baseline, Fluss as real-time layer **Pillar 6: Maintenance Operations** Lifecycle management for Iceberg metadata and files. - [ ] Snapshot Expiration: Configurable (default: disabled) - [ ] Orphan File Deletion: Configurable (default: disabled) **Pillar 7: Performance Benchmarking** Measuring and validating performance characteristics. - [ ] Tiering throughput, maximum table scalability, Union read performance GitHub link: https://github.com/apache/fluss/discussions/2342#discussioncomment-15520502 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
