Thanks Cheng For the FIP, the design overall looks good to me. >> When lake committer needs to find out the bucket end offset of committed >> lake snapshot, it has to reconstruct this information by reading the entire >> artificial bucket and offset columns from lake as Lance format lacks >> bucketing and partitioning support.
About this part, I think current approach is pretty in-efficient, could we kickoff a discussion to support custom options(properties) in lance community as well? Best, Leonard > 2025 7月 4 12:26，Wang Cheng <[email protected]> 写道： > > Hi all, > > > Lance is a popular table format designed for performant AI workloads. To > enable the integration between Fluss and the multimodal AI data lake > ecosystem, I'd like to propose FIP-5: Support tiering Fluss data to Lance [1]. > > > Any feedback and suggestions on this proposal are welcome! > > > [1]: > https://cwiki.apache.org/confluence/display/FLUSS/FIP-5%3A+Support+tiering+Fluss+data+to+Lance > > > > Regards, > Cheng > > > >
