FYI, I decided to pend this disccussion since we found a prerequisite need to be resolved. I'll go back to this disccussion after prerequisite is resolved.
Best regards, Yuxia ----- 原始邮件 ----- 发件人: "yuxia" <[email protected]> 收件人: "dev" <[email protected]> 发送时间: 星期三, 2025年 7 月 09日 下午 8:08:58 主题: [SPAM][DISCUSS] FIP-4: FlussLogScanner should support fetch log from tiered storage of datalake Hi, In Fluss design, datalake is considered as Fluss another tier storage. By saying datalake is a tier storage of Fluss, it always means that Fluss client can read from datalake as Fluss's data. But currently, we only support to tier Fluss data into datalake, but missing the reverse data flow. To address it, I'd like to propose FIP-4: FlussLogScanner should support fetch log from tiered storage of datalake[1] which aims to enable FlussLogScanner to support fetch log data from datalake tiered storage. Welcome your feedback and suggestions on this proposal. Looking forward to a productive discussion! [1]: [ https://cwiki.apache.org/confluence/display/FLUSS/FIP-3%3A+Support+tiering+Fluss+data+to+Iceberg | https://cwiki.apache.org/confluence/display/FLUSS/FIP-4%3A+FlussLogScanner+should+support+fetch+log+from+tiered+storage+of+datalake ] Best regards, Yuxia
