Skip to content

Conversation

@jhrotko
Copy link

@jhrotko jhrotko commented Dec 12, 2025

No description provided.

@jhrotko jhrotko force-pushed the register-extension-types branch from b9929fa to d6a5b9d Compare February 2, 2026 13:44
@jhrotko jhrotko force-pushed the register-extension-types branch from d6a5b9d to 3c3d2be Compare February 2, 2026 13:45
@jhrotko jhrotko force-pushed the register-extension-types branch from c030c56 to 961f16c Compare February 2, 2026 13:51
Copy link
Member

@lidavidm lidavidm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like the application should do this and not the driver? It would be surprising (IMO) to load a driver and have a bunch of extension types registered, especially as this is a global registry

@CurtHagenlocher
Copy link
Contributor

I feel like the application should do this and not the driver? It would be surprising (IMO) to load a driver and have a bunch of extension types registered, especially as this is a global registry

I wonder whether a driver ought to have a way to announce which extension types it uses.

@lidavidm
Copy link
Member

lidavidm commented Feb 3, 2026

Perhaps, but also for Flight SQL the set is unbounded/determined by the server, so apps should be prepared to handle unrecognized extension types (I sort of think Arrow libraries should be more consistent and either treat all extension types as pure metadata, or all extension types as a separate type even if unregistered)

@lidavidm
Copy link
Member

lidavidm commented Feb 3, 2026

Also, this doesn't do anything for usage outside of Go, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants