alamb opened a new pull request, #27057:
URL: https://github.com/apache/datafusion/pull/27057

   ## Which issue does this PR close?
   
   - Backport of #26893 to `branch-56` (for 56.0.0, tracked in #24461).
   - Related to #26866.
   
   ## Rationale for this change
   
   Backport of #26893 (from @cblp) to `branch-56` so that extension type 
display names in `DESCRIBE`, `SHOW COLUMNS` and `information_schema.columns` 
are part of the 56.0.0 release.
   
   ## What changes are included in this PR?
   
   Clean cherry-pick of 608ac9cef0 (#26893). No adaptation required; the diff 
is identical to the commit on `main`.
   
   - New `DFExtensionType::display_name` trait method (default `None`, so no 
behavior change for existing extension types).
   - New `datafusion_expr::extension_types::append_field_type_display_name` 
helper.
   - `InformationSchemaProvider::with_extension_type_registry` so `DESCRIBE`, 
`SHOW COLUMNS` and `information_schema.columns` can show the registered 
extension type name.
   - `DFUuid` displays as `UUID` and `DFJson` as `JSON`.
   
   ## Are these changes tested?
   
   Yes. Carries the original coverage: the `append_field_type_display_name` 
unit test in `datafusion-expr` and the additions to `sql_extension_types.slt`. 
Both pass on this branch, and clippy is clean on the touched crates.
   
   ## Are there any user-facing changes?
   
   Sessions that register extension types with a display name (such as the 
canonical `arrow.uuid` and `arrow.json`) now show that name in `DESCRIBE`, 
`SHOW COLUMNS` and `information_schema.columns`. The canonical extension types 
are not registered in a default session, so default output is unchanged. No 
breaking API changes: the new trait method has a default implementation.
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to