Thanks Keith for reviving this, and David & George for the FIP. +1 on narrowing scope. One point I'd like to check on Arrow Flight — my understanding is that the Arrow Flight SQL protocol in the FIP-32 <https://cwiki.apache.org/confluence/spaces/FLUSS/pages/406622520/FIP-32+Multiprotocol+Query+Gateway+for+Apache+Fluss> is a Flight SQL endpoint, which needs a SQL engine on the server side and thus depends on fluss-datafusion. If that's the case, since fluss-datafusion isn't ready yet (discussed in the fluss-rust roadmap), perhaps we could hold it off for 1.0 and narrow to just REST for the initial release, then add Flight SQL once fluss-datafusion lands. Please correct me if I'm misreading this.(My understanding is that plain Arrow Flight as a data-transport layer isn't part of this FIP — happy to discuss separately if there's demand.)
Happy to pick up part of the implementation once the scope settles. Best regards, Junbo Wang > On 31 Jul 2026, at 18:02, Keith Lee <[email protected]> wrote: > > David, George
