Is your feature request related to a problem or challenge?
After merging #21291 , we have a basic version of Arrow's canonical extension types (except Parquet Variant).
After quickly looking over the SQL AST Data Types, the following types should be considered:
- UUID: map to
arrow.uuid
- JSON: map to
arrow.json
- Timestamps with
TimezoneInfo::WithTimeZone: From what I can tell, it depends on the database on how this type is interpreted. Oracle seems to retain the time zone information for each datum, while we discard the timezone and normalize it based on the configured time zone.
Describe the solution you'd like
From what I can tell after quickly looking at the code we could change SqlToRel::convert_simple_data_type to retun a Field for the newly supported data types. Then add tests that showcase that the correct metadata is stored.
Describe alternatives you've considered
No response
Additional context
Is your feature request related to a problem or challenge?
After merging #21291 , we have a basic version of Arrow's canonical extension types (except Parquet Variant).
After quickly looking over the SQL AST Data Types, the following types should be considered:
arrow.uuidarrow.jsonTimezoneInfo::WithTimeZone: From what I can tell, it depends on the database on how this type is interpreted. Oracle seems to retain the time zone information for each datum, while we discard the timezone and normalize it based on the configured time zone.Describe the solution you'd like
From what I can tell after quickly looking at the code we could change
SqlToRel::convert_simple_data_typeto retun aFieldfor the newly supported data types. Then add tests that showcase that the correct metadata is stored.Describe alternatives you've considered
No response
Additional context