+1 for the API design Best, Leonard
> On 2025 Jul 28, at 13:46, yuxia <[email protected]> wrote: > > Hi, all. > Since this FIP has been pending for a while and not receive any more > comments. If still no further comments, I'll start to vote tomorrow. > > Best regards, > Yuxia > > ----- 原始邮件 ----- > 发件人: "wang junbo" <[email protected]> > 收件人: "dev" <[email protected]> > 发送时间: 星期二, 2025年 7 月 22日 下午 6:16:58 > 主题: [SPAM]Re: [DISCUSS] FIP-6: Decouple Flink union read with paimon > > +1 > Reviewed the existing Paimon union read code and the poc branch > <https://github.com/luoyuxia/fluss/tree/union-read-abstract> code, and > looking forward to the implementation of union read decoupling from Paimon.I > hope to contribute to its optimization and plan to write a blog to help > others understand it better. > > > > yuxia <[email protected]> 于2025年7月18日周五 15:29写道： > >> Currently, Flink's capability to unon read data in datalake and Fluss is >> tightly coupled with Paimon's implementation, which limits it's flexibility >> and extensibility. We hard code paimon related classes in fluss-flink >> module. It makes it difficult for Flink to support union read other >> datalakes and for other compute engines like spark, trino to integate with >> the union read ability. What's more, the tight coupling also obscures the >> core logic of union read , making the code harder to maintain and evolve. >> >> To address this , I’d like to propose FIP-6: Decouple Flink union read >> with paimon[1], which seeks to decouple union read from Paimon by >> introuding well-defiend interfaces and extension points which paimon should >> implement. By doing so, Flink can support a wider range of datalakes. >> Furthermore, the standardized interfaces will allow other compute engines >> to integrate with Fluss's union read capability. >> >> Welcome your feedback and suggestions on this proposal. Looking forward to >> a productive discussion! >> >> [1]: >> https://cwiki.apache.org/confluence/display/FLUSS/FIP-6%3A+Decouple+Flink+union+read+with+paimon >> >> Best regards, >> Yuxia >>
