Use PhysicalArrowCollector for __arrow_c_stream__ on relations#342
Merged
evertlammerts merged 2 commits intoduckdb:v1.5-variegatafrom Feb 25, 2026
Merged
Conversation
evertlammerts
changed the base branch from
vendoring-v1.5-variegata
to
v1.5-variegata
2 tasks
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 #137
This uses
PhysicalArrowCollectorto support arrow_c_stream on relations without having to materialize into duckdb native format first. Note that we can't useResultArrowArrayStreamWrapperbecause it callsTryFetchChunk, which isn't implemented onArrowQueryResult, so we have our own lightweight wrapper here.