DuckDB: use provided schema in query_arrow to avoid schema mismatches #483
+18
−14
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.
Summary
Update the
query_arrowmethod inDuckDbConnectionto use the providedprojected_schemaparameter instead of always fetching the schema manually from DuckDB.This makes query logic more robust by using exact target schema and avoids schema mismatch errors.
Benefits
LIMIT 0schema discovery query and avoids additional schema casts