Hi Fluss community, I'd like to start a discussion on FIP-25: Support In-Place Promotion of Existing Paimon Tables to Datalake-Enabled Fluss Tables[1].
This FIP proposes promoting an existing Paimon table to a datalake-enabled Fluss table in place through: CALL sys.enable_fluss_on_lake_table(...); "In-place" means reusing the existing Paimon table and historical data without creating a replacement table or rewriting the data to Paimon. Fluss creates the corresponding metadata, initializes historical primary-key state through Bulk Load when necessary, and validates schema and snapshot consistency before enabling datalake. Feedback and suggestions are welcome. [1]: https://cwiki.apache.org/confluence/spaces/FLUSS/pages/406623572/FIP-25+Support+In-Place+Promotion+of+Existing+Paimon+Tables+to+Datalake-Enabled+Fluss+Tables Best regards, Yuxia
