buvb commented on issue #2070: URL: https://github.com/apache/fluss/issues/2070#issuecomment-3663341380
Hi @wuchong, I've submitted a PR to address this issue: This PR implements schema evolution support for datalake-enabled tables (Paimon), specifically: https://github.com/apache/fluss/pull/2189 **Scope (MVP):** - Support `ADD COLUMN ... LAST` with `NULLABLE` columns only - Fluss as source of truth: schema changes are first applied to Fluss, then synchronized to Paimon - Idempotent retry handling for both Fluss and Paimon sides - Tiering compatibility during schema transition period **Key changes:** - [CoordinatorService]:Pass `LakeCatalog` to [alterTableSchema()] for Paimon sync - [MetadataManager]: Add [syncSchemaChangesToLake()] method - [SchemaUpdate]: Idempotent [addColumn()] - treat existing column with same type/comment as no-op - [PaimonLakeCatalog]: Handle `ColumnAlreadyExistException` as success for retry scenarios - [PaimonConversions]: Map Fluss `AddColumn` to Paimon `SchemaChange` - [FlussRecordAsPaimonRow]: Handle tiering when Fluss record is wider than Paimon schema **Tests:** - `LakeEnabledTableCreateITCase#testAlterLakeEnabledTableSchema` - `FlussRecordAsPaimonRowTest#testFlussRecordWiderThanPaimonSchema` - `FlussRecordAsPaimonRowTest#testPaimonSchemaWiderThanFlussRecord` This also closes #2128. Please review when you have time. Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
