Repository navigation
Export DuckDB chunked arrays across chunk boundaries - #11204
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When you read a
list<struct>column through the DuckDB extension, the read fails withchunked DuckDB export range 0..N crosses chunk boundary at Mas soon as the list elements span more than one chunk. The file reader gives this shape for any such column that is larger than one row group. The list exporter exports all its elements in one call, andChunkedExporteronly accepted ranges inside one chunk.ChunkedExporternow accepts any range:reuse_dictionaryvector over the cachedReusableDict. Nothing is copied, and DuckDB keeps the dictionary ID, so its dictionary caches still apply.