You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Jonathan Keane (Jira)" <ji...@apache.org> on 2021/10/15 13:12:00 UTC
[jira] [Resolved] (ARROW-13465) [R] to_arrow() from duckdb
[ https://issues.apache.org/jira/browse/ARROW-13465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Keane resolved ARROW-13465.
------------------------------------
Resolution: Fixed
Issue resolved by pull request 11032
[https://github.com/apache/arrow/pull/11032]
> [R] to_arrow() from duckdb
> --------------------------
>
> Key: ARROW-13465
> URL: https://issues.apache.org/jira/browse/ARROW-13465
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Jonathan Keane
> Assignee: Jonathan Keane
> Priority: Major
> Labels: pull-request-available
> Fix For: 6.0.0
>
> Time Spent: 8.5h
> Remaining Estimate: 0h
>
> With https://github.com/duckdb/duckdb/pull/2054 duckdb will have functionality to emit Arrow tables (and ideally record batches).
> We should document the workflow (and possibly write thin wrappers around these to make them consistent with other Arrow functions).
> This might be an opportunity to make a larger `to_arrow()` generic that can take either a duckdb query/table/reference or a pyarrow object (wrapping `py_to_r()`) so there's a unified interface for the purposes of getting arrow data out of known sources.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)