[
https://issues.apache.org/jira/browse/ARROW-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612723#comment-17612723
]
Apache Arrow JIRA Bot commented on ARROW-8047:
----------------------------------------------
This issue was last updated over 90 days ago, which may be an indication it is
no longer being actively worked. To better reflect the current state, the issue
is being unassigned per [project
policy|https://arrow.apache.org/docs/dev/developers/bug_reports.html#issue-assignment].
Please feel free to re-take assignment of the issue if it is being actively
worked, or if you plan to start that work soon.
> [Python][Documentation] Document migration from ParquetDataset to
> pyarrow.datasets
> ----------------------------------------------------------------------------------
>
> Key: ARROW-8047
> URL: https://issues.apache.org/jira/browse/ARROW-8047
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Documentation, Python
> Affects Versions: 0.16.0
> Reporter: Ben Kietzman
> Assignee: Joris Van den Bossche
> Priority: Critical
> Labels: pull-request-available
> Fix For: 10.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We need documentation describing a migration path from ParquetDataset, at
> least for the basic user facing API of ParquetDataset (As I read it, that's:
> construction, projection, filtering, threading, for a first pass). Following
> this we could mark ParquetDataset as deprecated, building features needed by
> power users like dask and adding those to the migration document
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
