cshuo opened a new pull request, #19044:
URL: https://github.com/apache/hudi/pull/19044

   ### Describe the issue this Pull Request addresses
   
   This PR strengthens `ITTestVectorDataSource` so Flink VECTOR behavior is 
validated across read projection, write validation, table schema metadata, 
Parquet physical encoding, and MERGE_ON_READ compaction paths.
   
   ### Summary and Changelog
   
   - Added projection coverage for queries that select VECTOR columns together 
with ordinary non-vector ARRAY columns.
   - Added coverage for VECTOR columns coexisting with regular `ARRAY<STRING>` 
columns.
   - Added small-to-large VECTOR dimension coverage for dimensions `2`, `128`, 
and `2048`.
   - Added write-time dimension mismatch validation coverage.
   - Added Parquet footer assertions for VECTOR metadata and fixed-length 
byte-array physical encoding.
   - Added MERGE_ON_READ VECTOR compaction coverage for both `avro` and 
`parquet` log block formats.
   - Added invalid VECTOR column configuration tests for missing fields, 
non-ARRAY fields, unsupported ARRAY element types, invalid dimensions, and 
duplicate VECTOR descriptors.
   
   ### Impact
   
   - **Functional impact**: No intended production behavior change; this PR 
only adds test coverage.
   - **Maintainability**: Improves regression coverage around Flink VECTOR 
behavior in `ITTestVectorDataSource`, including storage metadata and compaction 
paths that are easy to regress without targeted tests.
   - **Extensibility**: Provides reusable helpers for VECTOR dimension tables, 
compaction execution, Parquet footer inspection, and array endpoint assertions.
   
   ### Risk Level
   
   low. 
   
   ### Documentation Update
   
   none.
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Enough context is provided in the sections above
   - [ ] Adequate tests were added if applicable


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