thswlsqls opened a new issue, #8688: URL: https://github.com/apache/paimon/issues/8688
**Search before asking** - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. **Paimon version** master @ b7df2b487 / 2.0-SNAPSHOT **Compute Engine** Engine-agnostic (Vortex file format) **Minimal reproduce step** Define a table with the Vortex file format and a column of type `ARRAY<MAP<...>>` (or `ARRAY<VARIANT>`, `ARRAY<MULTISET<...>>`, `ARRAY<BLOB>`), then write to it. `VortexFileFormat.validateDataFields()` accepts the schema because `VortexRowTypeVisitor.visit(ArrayType)` (`paimon-vortex/paimon-vortex-format/.../VortexFileFormat.java`) returns without checking the array element type. The same unsupported types are rejected at the top level and inside `ROW` (`visit(RowType)` recurses into its fields, `visit(MapType)`/`visit(MultisetType)`/`visit(VariantType)`/`visit(BlobType)` throw). **What doesn't meet your expectations?** Expected: an `ARRAY` of an unsupported element type is rejected with a clear `UnsupportedOperationException` at validation time, like `MAP` at the top level. Actual: validation passes and the unsupported type surfaces later as an obscure failure in the native/Arrow write path. **Anything else?** `visit(ArrayType)` should recurse into the element type. `ARRAY` of supported types (e.g. `ARRAY<INT>`, `ARRAY<ARRAY<INT>>`) stays valid. **Are you willing to submit a PR?** - [x] I'm willing to submit a PR! -- 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]
