Antalya 26.3 Backport of #99521, #100150 - Add Arrow and Parquet format support for UUID data type#1774
Antalya 26.3 Backport of #99521, #100150 - Add Arrow and Parquet format support for UUID data type#1774mkmkme wants to merge 2 commits into
Conversation
…rquet-uuid Add Arrow and Parquet format support for UUID data type
…et-builder Improve Arrow Parquet writer to include UUID logical type
PR #1774 CI TriagePR: #1774 - Antalya 26.3 Backport of #99521, #100150 PR Change ScopeThis PR is focused on Arrow/Parquet UUID support:
No changes in Summary
Root Cause Classification1)
|
|
AI audit note: This review comment was generated by AI (gpt-5.3-codex). Audit update for PR #1774 (Arrow/Parquet UUID import-export support and inference paths): No confirmed defects in reviewed scope. Coverage summary: |
Note for reviewer
Besides 99521, 100150 was backported as well as a follow-up PR fixing an issue in 99521. The tests are passing locally (apart from ones that couldn't run on the local machine)
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Adds native support for importing and exporting UUID data types in Arrow and Parquet formats. Users can now directly query and transfer UUID data between ClickHouse and other data tools without requiring manual string conversions or workarounds. Automated logical inference for top-level UUIDs, and support for explicit schema hint for nested UUIDs (ClickHouse#99521 by @ivanmantova).
Exporting UUIDs to Parquet via the Arrow encoder now includes the correct UUID type annotation, eliminating the need to manually cast
FixedString(16)data when reading the files back into ClickHouse or other systems (ClickHouse#100150 by @ivanmantova).Documentation entry for user-facing changes
...
CI/CD Options
Exclude tests:
Regression jobs to run: