You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Joris Van den Bossche (Jira)" <ji...@apache.org> on 2022/04/05 11:29:00 UTC

[jira] [Updated] (ARROW-13074) [Python] Start with deprecating ParquetDataset custom attributes

     [ https://issues.apache.org/jira/browse/ARROW-13074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joris Van den Bossche updated ARROW-13074:
------------------------------------------
        Parent: ARROW-16119
    Issue Type: Sub-task  (was: Improvement)

> [Python] Start with deprecating ParquetDataset custom attributes
> ----------------------------------------------------------------
>
>                 Key: ARROW-13074
>                 URL: https://issues.apache.org/jira/browse/ARROW-13074
>             Project: Apache Arrow
>          Issue Type: Sub-task
>          Components: Python
>            Reporter: Joris Van den Bossche
>            Assignee: Joris Van den Bossche
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 5.0.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> As a first step for ARROW-9720, we should start with deprecating attributes/methods of {{pq.ParquetDataset}} that we would definitely not keep / are conflicting with the "dataset API". 
> I am thinking of the {{pieces}} attribute (and the {{ParquetDatasetPiece}} class), the {{partitions}} attribute (and the {{ParquetPartitions}} class). 
> In addition, some of the keywords are also exposed as properties (memory_map, read_dictionary, buffer_size, fs), and could be deprecated.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)