Apache Fluss Community call(28 August) summary
Key Takeaways
- 1.0 Release Imminent: Feature freeze is targeted for EOD Friday. The
release will include the new Gateway and the historical partition lookup
feature (marked "experimental").
- Gateway (FIP-49) Delivered: The core Gateway is merged, unblocking 1.0.
Its initial scope covers metadata discovery, management, and REST writes,
with lookups and auth deferred to future releases.
- New Proposal (FIP 53) for Log Scanner: A new FAPE was proposed to add
persistent offsets and cooperative consumption to the Log Scanner,
addressing key reliability and rebalancing gaps.
- Community Engagement: A GitHub issue was created to list companies
using Flues, building confidence for new adopters. A hackathon is planned
for the Community Over Code conference in October.
Topics
1.0 Release Status & Feature Freeze
- Progress: Significant progress has been made since the missed Aug 14
target, with the release now very close.
- Blockers: The remaining blockers are mostly small doc updates, but a
few critical issues require immediate attention:
- Flink catalog losing NOT NULL constraint on complex types →
potential data corruption.
- Hadoop dependency update.
- Other stability and security issues.
- Feature Freeze Plan:
- Target: EOD Friday.
- Rationale: To accommodate key contributors from Alibaba who will be
on vacation next week.
- Process: Cut a 1.0 branch after freeze → begin release testing.
- Timeline: The final release date is uncertain, pending testing and
the Apache voting process, but is estimated at ~2 weeks post-freeze.
Feature Scope & Readiness
- Historical Partition Lookup:
- Decision: Include in 1.0, but mark as "experimental" in docs.
- Rationale: The feature is not yet production-ready. This approach
allows users to test it in non-critical environments and provide feedback
for a more robust 1.1 release.
- Row-Level TTL:
- Status: Merged.
- Readiness: Production-ready, validated in Alibaba Cloud's
environment.
- Support: Alibaba contributors will provide support.
- Deletion Vectors:
- Status: POC branch is ready.
- Blocker: Awaiting review from Jark Wu on the end-to-end flow for
Paimon and Iceberg tables.
- Next: Mehul will share the FIP and a demo video once the review is
complete.
Gateway (FIP 49) Update
- Status: Merged and ready for 1.0.
- Initial Scope: Metadata discovery, metadata management, and REST write.
- Deferred Scope: REST lookups and authentication are planned for future
releases.
- Final Task: Merge the PR for the container image and release pipeline
today.
Log Scanner Offset Management (FIP 53)
- Problem: The current Log Scanner lacks persistent offsets and
cooperative consumption, leading to data loss on client crashes and
preventing multiple scanners from reading a single table.
- Proposal: FIP 53 introduces:
- Persistent Offsets: Store offsets and group metadata in a
server-side key table.
- Scanner Groups: A server-side mechanism to assign buckets to group
members, ensuring each bucket is read exactly once and enabling rebalancing.
- Admin APIs: For managing groups and resetting offsets.
- Next: Jie Lu will post the FIP to the mailing list for community
discussion and a vote.
Community & Events
- Company Usage List: A GitHub issue was created to list companies using
Flues. This builds confidence for new adopters and helps the community
prioritize features.
- Upcoming Events:
- Community Over Code (October): Flues will have two talks and a
hackathon. The community is invited to propose hackathon topics.
Next Steps
- All Contributors:
- Review 1.0 blocker PRs (priority: blocked) to help meet the feature
freeze.
- Add your company to the "Who's using Flues?" GitHub issue.
- Keith & Leonard:
- Coordinate with contributors to finalize the feature freeze plan
(EOD Friday or Monday).
- Ensure 1.0 documentation clearly labels experimental features.
- Jie Lu:
- Post FIP 53 to the mailing list for discussion and a vote.
- Mehul Batra:
- Share the Deletion Vector FIP and a demo video after Jark's review
is complete.
- Anton Borisov:
- Collect hackathon topics for the Community Over Code event.
Recoding: https://fathom.video/share/DzAGxvjn-QMxiqJNpVkq5tvsCSDqEba_
пт, 28 авг. 2026 г. в 06:52, Forward Xu <[email protected]>:
> Hi everyone,
>
> I'm sorry for the short notice, but something came up unexpectedly this
> afternoon, and I won't be able to join the community call as planned.
>
> My apologies for any inconvenience this may cause. I'll be sure to follow
> up on the notes and any decisions afterward, and I look forward to catching
> up on the discussion.
>
> Thanks for your understanding.
>
> Best regards,
>
> Forward
>
> Zhe Wang <[email protected]> 于2026年8月25日周二 21:50写道：
>
> > Hi Anton,
> >
> > Thanks for setting this up — the CST 16:00 slot works well for me.
> > I'll join on Friday.
> >
> > Looking forward to the discussion.
> >
> > Best regards,
> > Zhe Wang
> >
> >
> > Forward Xu <[email protected]> 于2026年8月22日周六 16:57写道：
> >
> > > Hi Anton,
> > >
> > > Thanks for setting this up. I will join on Friday (CST 16:00).
> > >
> > > Looking forward to the discussion.
> > >
> > > Best,
> > > Forward
> > >
> > > Anton Borisov <[email protected]> 于2026年8月22日周六 16:37写道：
> > >
> > > > Hi everyone,
> > > >
> > > > We’re excited to invite you to our upcoming Fluss community call on
> > > > *Friday,
> > > > August 28th*.
> > > >
> > > > Please feel free to join and bring any topics or agenda items you’d
> > like
> > > to
> > > > discuss. It’s a great opportunity to share feedback, bring real-world
> > > > production insights, discuss ongoing work, and help shape the
> > priorities
> > > > that matter most to the community.
> > > >
> > > > Join using Community Events [1]
> > > >
> > > > -
> > > >
> > > > Europe (CEST): 10:00–10:45 AM
> > > > -
> > > >
> > > > UK (BST): 9:00–9:45 AM
> > > > -
> > > >
> > > > India (IST): 1:30–2:15 PM
> > > > -
> > > >
> > > > China (CST): 4:00–4:45 PM
> > > > -
> > > >
> > > > US West Coast (PDT): 1:00–1:45 AM
> > > >
> > > > Add discussion points here: Community Sync Docs [2]
> > > >
> > > > Looking forward to the discussion and hearing your thoughts!
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://calendar.google.com/calendar/u/0?cid=MjUzMjY2OTFkY2FmNmRiYjk5MzllZmUxNDliYjg1ZjI4ODhhNjU0YzY5Mzc2M2IyZDQ1NzIwNTAyZGU1MjZmOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
> > > >
> > > > [2]
> > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/18b7G_dvYx-1FogV7LWEFMHXze5D5T9XZ3h9zSU75dDA/edit?tab=t.0#heading=h.w6zqoksn877i
> > > >
> > > > -- Anton
> > > >
> > >
> >
>
