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

   ### Purpose
   
     Linked issue: https://github.com/apache/fluss/issues/3277
   
     This PR introduces the Hudi lake source reader implementation so Fluss can 
read records from Hudi lake splits.
   
     The reader bridges Hudi/Flink row data to Fluss lake source records, 
including user row projection, system column extraction, offset/timestamp 
propagation, and row kind conversion.
   
   ### Brief change log
   
     - Implement `HudiLakeSource#createRecordReader` and wire projection into 
the Hudi reader path.
     - Add `HudiRecordReader` to convert Hudi `RowData` into Fluss `LogRecord`.
     - Add `UnifiedHudiTableReader` to read both COW parquet file slices and 
MOR file group slices.
     - Add Flink-to-Fluss data adapters for row, array, and map values.
     - Add `RowKind` to `ChangeType` conversion utility.
     - Add unit tests for Hudi source reader conversion and Flink row adapter 
behavior.
     - Update `HudiLakeSourceTest` to cover reader creation error wrapping.
   
   ### Tests
   
     - `mvn -pl fluss-lake/fluss-lake-hudi -am -DskipITs -Dcheckstyle.skip=true 
-DfailIfNoTests=false test`
   
     Result:
   
     - `fluss-lake-hudi`: 67 tests passed, 0 failures, 0 errors, 0 skipped.
     - `git diff --check`: passed.
   
    ## API and Format
   
     This change does not introduce public API changes.
   
     This change does not change Fluss storage format or network protocol 
format. It adds a Hudi lake source reader implementation and internal 
conversion adapters.
   
   ### Documentation
   
     No documentation update is included in this PR.
   
     The change enables Hudi lake source reading internally, but does not add 
new user-facing configuration options.


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