Hello Yuxia! Thanks for the great FIP! I have some questions: 1. Isn't the scope of the FIP misleading? It seems this FIP is about removing system columns, but it primarily proposes a new read mode named PARTITION_TIMESTAMP.
2. How does this relate to union reads? I am quite new to the community and Fluss. Could you explain how the new PARTITION_TIMESTAMP mode relates to union reads? If the answer is not obvious, perhaps this warrants a section in the FIP. Thank you! On Tue, Jan 20, 2026 at 8:20 AM yuxia <[email protected]> wrote: > Hi, all. > > Currently, every Fluss lake table is automatically provisioned with three > mandatory system columns, __bucket , __offset , __timstamp (intended for > bucket and offset-based subscription as well as addition informartion > check). > While originally designed to allow clients to pinpoint specific data > offsets of specific buckets, the practical evolution of the ecosystem has > rendered this default behavior suboptimal for the dowstream since the > dowstream warehouse or BI tools do not expect these internal metadata > fields. > > > So, I'd like to propose FIP-27: Remove Mandatory System Columns From Fluss > Lake Tables [1] to remove the three mandatory system columns while still > keep compability. > > Welcome your feedback and suggestions on this proposal. Looking forward to > a productive discussion! > > [1]: > https://cwiki.apache.org/confluence/display/FLUSS/FIP-27%3A+Remove+Mandatory+System+Columns+From+Fluss+Lake+Tables > > Best regards, > Yuxia > -- Lorenzo Affetti Senior Software Engineer @ Flink Team Ververica <http://www.ververica.com>
