Quick correction: This roadmap was drafted in collaboration with Yuxia, not just by me alone. Best, Mehul Batra
On Sat, Jan 17, 2026 at 12:18 AM Mehul Batra <[email protected]> wrote: > Hi Jark and everyone, > > Thanks for kicking off this discussion! I've been actively working on the > Fluss x Iceberg integration and wanted to share our 2026 roadmap for this > critical area. > > I've drafted a comprehensive roadmap focusing on 7 key pillars that align > with both lakehouse and real-time analytics requirements: > https://github.com/apache/fluss/discussions/2342#discussioncomment-15520502 > > *Key highlights:* > > - Iceberg V3 support (Deletion Vectors, Variant datatype, etc.) > - Multi-catalog ecosystem (AWS Glue, Unity, Polaris) > - Performance optimizations for Union reads and deletes > - In-place lakehouse integration (define Fluss tables on existing > Iceberg data) > > For those running or evaluating Fluss with Iceberg: > > - *What are your top 3 priorities* from the roadmap above? > - *Which catalog integrations* are most critical for your use case? > - *Are there any gaps* in the current Iceberg integration that block > your adoption? > > Looking forward to hearing feedback from the community to refine > priorities and ensure we're building what matters most. > > Best, > Mehul Batra > > On Sun, Jan 11, 2026 at 9:29 PM Jark Wu <[email protected]> wrote: > >> Thanks Giannis, >> >> I added those. >> Besides, I added "Coordinator HA" and "Geo-Replication" >> >> Best, >> Jark >> >> On Sun, 11 Jan 2026 at 22:50, Giannis Polyzos <[email protected]> >> wrote: >> > >> > Maybe it’s worth adding: >> > 1. Multi-stream Delta Join >> > 2. Support for Apache Hudi >> > >> https://cwiki.apache.org/confluence/display/FLUSS/FIP-24%3A+Support+tiering+Fluss+data+to+Hudi >> > >> > And highlight we will keep strengthening the current >> Paimon/Iceberg/Lance >> > integrations ?? >> > >> > >> > >> > On Sun, 11 Jan 2026 at 9:56 AM, Giannis Polyzos <[email protected]> >> > wrote: >> > >> > > Thanks for putting this together Jark 🙏 >> > > >> > > Big +1 for this and it’s exciting to say the least. Once we finalise >> we >> > > can share publicly and get as much feedback as possible. >> > > >> > > I think this roadmap will also provide more clarity on the direction >> and >> > > vision of Fluss and will get more people exciting - hopefully also >> help get >> > > more contributions. >> > > >> > > Best, >> > > Giannis >> > > >> > > On Sun, 11 Jan 2026 at 9:54 AM, Jark Wu <[email protected]> wrote: >> > > >> > >> Hi everyone, >> > >> >> > >> As we step into 2026, I’d like to kick off a collaborative discussion >> > >> around the Fluss Roadmap for 2026 to align our community efforts, set >> > >> clear priorities, and ensure Fluss continues to evolve in a direction >> > >> that best serves real-world use cases, especially in streaming, >> > >> lakehouse, and AI workloads. >> > >> >> > >> I’ve drafted an initial set of themes and focus areas based on recent >> > >> contributions and user feedback: >> > >> >> > >> 👉 https://github.com/apache/fluss/discussions/2342 >> > >> >> > >> If you are running Fluss in production or evaluating it for your >> > >> next-gen architecture, your feedback is critical. It's very welcome >> to >> > >> comment here or in the GitHub Discussion thread about: >> > >> >> > >> * Blockers: What is missing that prevents you from deploying Fluss >> today? >> > >> * Priorities: Which feature below would provide the most immediate >> > >> value to your team? >> > >> * AI & Lakehouse: Which specific integration do you expect the most? >> > >> >> > >> >> > >> Side note: Once the 2026 roadmap is finalized, I suggest replacing >> the >> > >> current roadmap page on the website ( >> https://fluss.apache.org/roadmap) >> > >> with this version by linking to the GitHub discussion link. This >> makes >> > >> it easier to maintain and keep up to date, as it stays naturally >> > >> synchronized with actual GitHub development progress. >> > >> >> > >> >> > >> Best, >> > >> Jark Wu >> > >> >> > > >> >
