[ 
https://issues.apache.org/jira/browse/ARROW-11782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291698#comment-17291698
 ] 

Ben Kietzman commented on ARROW-11782:
--------------------------------------

IIUC, python and R only use ScanTasks when materializing a stream of 
RecordBatches instead of using Scanner::ToTable. That functionality could 
easily be moved upstream into C++ by providing Scanner::GetRecordBatches or 
similar, which would be easier to consume from bindings in any case. Therefore 
I'd say the wrappers for ScanTask could also be removed from Python and R.

If that's not acceptable, I'd think that ARROW-7001 should prefer to add 
{{ScanTask::ExecuteAsync}} and refactor {{ScanTask::Execute}} to be a backwards 
compatible wrapper.

[~jorisvandenbossche] [~npr] [~westonpace]

> [GLib][Dataset] Remove bindings for internal classes
> ----------------------------------------------------
>
>                 Key: ARROW-11782
>                 URL: https://issues.apache.org/jira/browse/ARROW-11782
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: GLib
>    Affects Versions: 3.0.0
>            Reporter: Ben Kietzman
>            Priority: Major
>             Fix For: 4.0.0
>
>
> GLib and ruby include bindings for internal classes such as ScanOptions, 
> ScanContext, InMemoryScanTask, ScanTask, ... These are probably unnecessary 
> and should be removed to present a simpler interface less prone to breakage 
> under refactoring of the wrapped classes 
> https://github.com/apache/arrow/pull/9532/checks?check_run_id=1974229719#step:8:2071



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to