[
https://issues.apache.org/jira/browse/ARROW-12231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Li updated ARROW-12231:
-----------------------------
Description:
>From ARROW-10882/[https://github.com/apache/arrow/pull/9802]
* Backing an InMemoryDataset with a reader is misleading. Let's split that out
into a separate class.
* Dataset scanning can then use an I/O thread for the new class. (Note that
for Python, we'll need to be careful to release the GIL before any operations
so that the I/O thread can acquire the GIL to call into the underlying Python
reader/file object.)
* Longer-term, we should interface with Python's async.
was:
>From ARROW-10882/[https://github.com/apache/arrow/pull/9802]
* Backing an InMemoryDataset with a reader is misleading. Let's split that out
into a separate class.
* Dataset scanning can then use an I/O thread for the new class.
* Longer-term, we should interface with Python's async.
> [C++][Dataset] Separate datasets backed by readers from InMemoryDataset
> -----------------------------------------------------------------------
>
> Key: ARROW-12231
> URL: https://issues.apache.org/jira/browse/ARROW-12231
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 4.0.0
> Reporter: Weston Pace
> Assignee: David Li
> Priority: Major
> Labels: dataset, datasets
>
> From ARROW-10882/[https://github.com/apache/arrow/pull/9802]
> * Backing an InMemoryDataset with a reader is misleading. Let's split that
> out into a separate class.
> * Dataset scanning can then use an I/O thread for the new class. (Note that
> for Python, we'll need to be careful to release the GIL before any operations
> so that the I/O thread can acquire the GIL to call into the underlying Python
> reader/file object.)
> * Longer-term, we should interface with Python's async.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
