wzx140 opened a new pull request, #3476:
URL: https://github.com/apache/fluss/pull/3476

   ## Summary
   - Support custom Paimon lake table path with `table.datalake.database-name` 
and `table.datalake.table-name`.
   - Route Flink `$lake` reads and Paimon tiering creation/writes to the 
mapping lake table path.
   - Route all alter lake requests to the mapping lake table path.
   - Clear existing tiering progress when lake table path mapping parameters 
change, so later tiering starts from the beginning for the new sink table.
   - Allow `paimon.path` to be changed only together with lake table path 
mapping parameters; reject standalone `paimon.path` alteration.
   - Reject custom lake table path mapping for Spark lake reads in this phase.
   
   ## UT Coverage
   - `FlinkCatalogTest#testGetLakeTableWithCustomLakePath`: verifies Flink 
catalog resolves `$lake` and metadata-table reads to the custom lake 
database/table.
   - 
`FlinkUnionReadPrimaryKeyTableITCase#testUnionReadWithCustomLakeTablePath`: 
verifies Flink union read can read from the mapped Paimon lake table and merge 
lake data with the Fluss tail.
   - `PaimonTieringITCase#testTieringWithCustomLakeTablePath`: verifies Paimon 
tiering creates/writes the lake table at the custom mapped path and records the 
expected snapshot progress.
   - `LakeEnabledTableCreateITCase#testAlterLakePathOptionsValidation`: 
verifies lake path mapping options can be altered while datalake is disabled, 
and cannot be altered after datalake is enabled.
   - 
`LakeEnabledTableCreateWithHiveCatalogITCase#testAlterPaimonPathRequiresLakePathOptions`:
 verifies standalone `paimon.path` alteration is rejected, while `paimon.path` 
altered together with mapping options is accepted and used when enabling 
datalake with HiveCatalog.
   - 
`CoordinatorEventProcessorTest#testAlterLakePathClearsProgressWhenDatalakeDisabled`:
 verifies changing lake path mapping while datalake is disabled clears existing 
tiering progress.


-- 
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]

Reply via email to