[
https://issues.apache.org/jira/browse/ARROW-13074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391457#comment-17391457
]
Joris Van den Bossche commented on ARROW-13074:
-----------------------------------------------
There is actually some replacement (but not 1:1) if you use the Datasets API,
see ARROW-8655 /
https://github.com/apache/arrow/pull/10661#issuecomment-874672918. That added a
{{partitioning}} attribute with similar information.
Can you check if that gives sufficient information for your use case?
Now, we should certainly better document this / mention it in the deprecation
message (I worked on both changes simultaneously, but should afterwards have
updated the deprecation message that an alternative exists). We should maybe
also expose the {{partitioning}} attribute on ParquetDataset (if constructed
with {{use_legacy_dataset=False}}), as I did for the
{{filesystem}}/{{files}}/{{fragments}} attributes.
> [Python] Start with deprecating ParquetDataset custom attributes
> ----------------------------------------------------------------
>
> Key: ARROW-13074
> URL: https://issues.apache.org/jira/browse/ARROW-13074
> Project: Apache Arrow
> Issue Type: Improvement
> 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.3.4#803005)
