The GitHub Actions job "CI" on fluss.git/main has failed.
Run started by GitHub user polyzos (triggered by polyzos).

Head commit for run:
5603486aeea678fc3c68e8a03d5afb1a2cdd6980 / ForwardXu <[email protected]>
[fluss-client] Support Complex Data Types on the Java API (NestedRow/ROW) 
(#2900)

* [fluss-client] Support Complex Data Types on the Java Typed API 
(NestedRow/ROW)

- Add ROW type support in PojoToRowConverter (POJO -> GenericRow)
- Add ROW type support in RowToPojoConverter (InternalRow -> POJO)
- Add ROW type validation in ConverterCommons
- Add ROW element support in PojoTypeToFlussTypeConverter (for Array/Map)
- Add ROW element support in FlussArrayToPojoArray (for Array<ROW>)
- Add comprehensive tests for nested ROW, deeply nested ROW, ROW with
  Array/Map fields, Array<ROW>, Map<K, ROW>, null handling, and validation
- Update java-client.md documentation with ROW type mapping and usage examples

* fix: address PR review feedback for nested ROW typed API

1. Pre-compile PojoToRowConverter in write path for ROW elements
   - PojoArrayToFlussArray: cache converter for ARRAY<ROW> elements
   - PojoMapToFlussMap: cache converter for ROW-typed map keys/values
   - Avoids re-creating converter per element (reflection + field scan)

2. Fix type-unsafe round-trip for Map<K, POJO> with ROW value type
   - Add genericType field to PojoType.Property to preserve generic info
   - FlussMapToPojoMap now accepts keyClass/valueClass parameters
   - RowToPojoConverter extracts ParameterizedType args for MAP fields
   - Map<String, AddressPojo> now correctly round-trips as AddressPojo

3. Migrate tests to proper locations
   - Move nested ROW POJOs to ConvertersTestFixtures
   - Move write tests to PojoToRowConverterTest
   - Move round-trip tests to RowToPojoConverterTest
   - Delete standalone NestedRowConverterTest

* add some improvements

* fix checkstyle

---------

Co-authored-by: ipolyzos <[email protected]>

Report URL: https://github.com/apache/fluss/actions/runs/24290229697

With regards,
GitHub Actions via GitBox

Reply via email to