You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue arises from my question in Mastodon and the answer by @krlmlr.
For DBI to take full advantage of Arrow support in DuckDB, e.g. if the DuckDB table has been created with arrow::to_duckdb(), the resulting lazy object would need its driver to transfer the arrow object without converting to a data frame first. I understand from @krlmlr that it is now converted to a data frame by duckdb::dbGetQueryArrow().
This issue arises from my question in Mastodon and the answer by @krlmlr.
For DBI to take full advantage of Arrow support in DuckDB, e.g. if the DuckDB table has been created with
arrow::to_duckdb()
, the resulting lazy object would need its driver to transfer the arrow object without converting to a data frame first. I understand from @krlmlr that it is now converted to a data frame byduckdb::dbGetQueryArrow()
.Created on 2024-05-08 with reprex v2.1.0
Session info
The text was updated successfully, but these errors were encountered: