Hey Forward, Yes that‘s the main advantage that this gateway should provide. Easily integrate other protocols with a couple hundred lines of code, as the Gateway handles the main interaction with Fluss.
Best regards David > On 7. Mar 2026, at 05:13, ForwardXu <[email protected]> wrote: > > > Hi David, > > Thanks a lot for sharing the FIP-32 draft and George’s prototype work on the > multiprotocol query gateway! > > Supporting multiple protocols (especially Flight SQL) via Apache DataFusion > is a great direction for Fluss, and I fully support this initiative. > > I’ve checked the repo and have one quick question: will this gateway be > designed to be pluggable, so that we can easily add new protocols in the > future? > > Looking forward to further discussions, and I’m happy to help with any > reviews or testing. > > Best, > Forward > 原始邮件 > 发件人：David Reger <[email protected]> > 发件时间：2026年3月7日 07:39 > 收件人：dev <[email protected]> > 主题：[DISCUSS] FIP-32 Multiprotocol Query Gateway for Apache Fluss > > Hey together, > > Thanks to George we have already a nice draft of a query gateway using Apache > Datafusion du support multiple protocols especially Flight SQL. > > His Repo is here > https://github.com/gstamatakis95/fluss/tree/feature/query-gateway. > > Based on his work I created a FIP to further discuss how the query gateway > fits into the project and how we want to integrate and extend it further. > > You can find the FIP Draft here > https://drive.google.com/file/d/1CC_uSQjtQmlMNGZyyHXr9K162BpKZvZO/view?usp=drivesdk > > Thank you and I appreciate every feedback. > > Kind regards > David > >
