Cache arrow schema for streaming types#423
Merged
evertlammerts merged 2 commits intoduckdb:v1.5-variegatafrom Apr 9, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes https://github.com/duckdblabs/duckdb-internal/issues/8834
Fetching the arrow schema now tries to start a transaction if there is no valid client context (duckdb/duckdb#21927). This needed for the geoparquet arrow extension. Since streams are lazy, the connection is often already closed when a stream is consumed.
This fix caches the schema in favor of keeping the connection open for the lifetime of the streams. This is part of a larger discussion on how to handle connection state in lazy arrow streams and it's likely that we want to solve this differently in 2.0.