[
https://issues.apache.org/jira/browse/ARROW-13074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17375872#comment-17375872
]
Weston Pace commented on ARROW-13074:
-------------------------------------
[~ldacey] Does "basename_template" provide the functionality you seek? It's
currently documented as "A template string used to generate basenames of
written data files. The token '\{i}' will be replaced with an automatically
incremented integer. If not specified, it defaults to "part-\{i}." +
format.default_extname" I seem to recall there was some earlier discussion of
this on a related Jira but I don't remember which one.
> [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: 40m
> 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)
