You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/07/17 08:36:00 UTC
[jira] [Updated] (ARROW-16719) [Python] Add path/URI /+ filesystem handling to parquet.read_metadata
[ https://issues.apache.org/jira/browse/ARROW-16719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ARROW-16719:
-----------------------------------
Labels: good-first-issue pull-request-available (was: good-first-issue)
> [Python] Add path/URI /+ filesystem handling to parquet.read_metadata
> ---------------------------------------------------------------------
>
> Key: ARROW-16719
> URL: https://issues.apache.org/jira/browse/ARROW-16719
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
> Reporter: Joris Van den Bossche
> Priority: Critical
> Labels: good-first-issue, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently you can pass a local file path or file-like object, or a URI (eg "s3://...") or path+filesystem combo to {{parquet.read_table}}.
> But the {{parquet.read_metadata}} and {{parquet.read_schema}} methods (being a small wrapper around {{ParquetFile}} only accept the local file path or file-like object. I would propose to add the same path+filesystem handling to those functions as happens in {{read_table}} to make the capabilities of those consistent.
> (I ran into this in geopandas, where we use {{read_table}} to read the actual data, but also need {{read_metadata}} to inspect the actual Parquet FileMetaData for metadata)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)