*Recording:*

https://fathom.video/share/gsVkU3_i2ex_W8wLcRJhq4XmXSv8zgso

*Meeting Notes:*

Fluss-Client 0.1 Release Candidate
Status: The flues-client 0.1 RC is live for community voting.

   - Blockers:Votes: Requires one more binding vote to proceed.
   - Title: The voting thread title needs correction from FruitsCand to
   FruitsRust.


   - Binaries: The RC lacks binary distributions for the Rust client.
   - Announcement: Two blog posts are ready: a general release announcement
   and a technical deep-dive on the Rust client.

Fluss v1.0 Release Progress (Target: June 15)

   - Filter Pushdown: ~50% of code changes merged.
   - KBSCAN Prime Key: FIP discussion ongoing; most concerns addressed.
   - Multi-Location Remote Storage: Some PRs merged.
   - Multi-Disk Local Storage: FIP 33 is live for review.
   - Variant Data Type: Design in progress to support complex data while
   preserving column projection pushdown. FIP expected next month.
   - Colony A: PRs under review; merge expected soon.

Fluss AI Native Initiative

   - Goal: Add an AI-native CLI and skills to the v1.0 release to
   accelerate adoption for new users.
   - Rationale: As a young project, Fluss can leverage AI tools to close
   the adoption gap with mature projects like Kafka.
   - Initial Scope: A simple CLI and basic skills built on the Rust client.
   - Standardization: Use the agents.md convention for universal skills
   compatibility across AI tools (e.g., Cloud Code, Codecks).

LanceDB Integration Roadmap
Problem: The current integration provides little value beyond fresh data
ingestion.
Proposed Solution: A "union read" feature to query real-time Fluss data and
historical LanceDB data together.

   - Debate: Vector Search StrategyOption 1 (Incremental): Start with a
   simple brute-force search.Pro: Easy first step for small, real-time
   datasets.


   - Con: Useless for large-scale data; risks losing user trust.


   - Option 2 (Robust): Implement proper vector indexes (e.g., HNSW).Pro:
   Essential for true AI-native capabilities.


   - Con: Architecturally complex; requires significant CPU/memory.


   - Compromise: A plugin architecture (like Postgres's pgvector) could
   allow for incremental improvements.
   - Architectural Decision: The team must first choose a storage model
   (in-memory vs. object store) as they require vastly different architectures.

Iceberg Deletion Vector Support
Status: A POC is complete, demonstrating a viable design.
Goal: Resolve Iceberg's real-time update pain points.

   - Benefits:Faster query performance on primary key tables.


   - Efficient CDC (Change Data Capture) ingestion.
   - Timeline: Design discussion on the dev channel targeted for next month.

Fluss Query Gateway (FIP 32)
Context: FIP 32 proposes a query gateway for Fluss.
Decision: Merge the FlussRust repo into the main Fluss repo
post-flues-client 0.1 release.Rationale: Consolidates community effort and
accelerates development.

   - Gateway Scope:Phase 1: A pluggable REST gateway for the CLI to
   communicate with the cluster.


   - Phase 2: A separate proposal for a protocol layer (e.g., Postgres,
   Kafka).
   - Kafka Protocol: A full Kafka protocol implementation is a separate,
   larger effort that belongs in the data server, not the gateway.



Best Regards,
Mehul Batra

On Tue, Mar 24, 2026 at 1:07 PM Mehul Batra <[email protected]>
wrote:

> Hi everyone,
> We’re excited to invite you to our upcoming Fluss community call on
> Friday, March 27th. Please feel free to join and bring along any topics or
> agenda items you’d like to discuss.
> It’s a great opportunity to share your feedback, bring in real-world
> production insights, and help shape the priorities that matter most to the
> community.
> Looking forward to the discussion and hearing your thoughts!
> Join using: Community Events
> <https://calendar.google.com/calendar/u/0?cid=MjUzMjY2OTFkY2FmNmRiYjk5MzllZmUxNDliYjg1ZjI4ODhhNjU0YzY5Mzc2M2IyZDQ1NzIwNTAyZGU1MjZmOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t>
> Europe (CET): 9:00 – 9:45 AM
> India (IST): 1:30 – 2:15 PM
> China (CST): 4:00 – 4:45 PM
> US (PDT): 1:00 – 1:45 AM
> Add discussion points here: Community Sync Docs
> <https://docs.google.com/document/d/18b7G_dvYx-1FogV7LWEFMHXze5D5T9XZ3h9zSU75dDA/edit?tab=t.0#heading=h.w6zqoksn877i>
> Best Regards,
> Mehul Batra
>

Reply via email to