You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Jorge Leitão (Jira)" <ji...@apache.org> on 2020/10/29 17:47:00 UTC
[jira] [Resolved] (ARROW-10389) [Rust][DataFusion] Make the custom
source implementation API more explicit
[ https://issues.apache.org/jira/browse/ARROW-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jorge Leitão resolved ARROW-10389.
----------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Issue resolved by pull request 8527
[https://github.com/apache/arrow/pull/8527]
> [Rust][DataFusion] Make the custom source implementation API more explicit
> --------------------------------------------------------------------------
>
> Key: ARROW-10389
> URL: https://issues.apache.org/jira/browse/ARROW-10389
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Rust, Rust - DataFusion
> Reporter: Remi Dettai
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> As you can see in [ARROW-10368|https://issues.apache.org/jira/browse/ARROW-10368], I had quite a hard time figuring out that the TableProvider trait could be used to provide custom source implementations for DataFusion.
> I think that adding a {{read_table(provider: Box<dyn TableProvider + Send + Sync>) -> Result<Arc<dyn DataFrame>>}} method to the ExecutionContext and an example in the tests and/or in the examples folder would make the API more explicit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)