Skip to content

ENH: Need new semantics for selecting parquet engine in Pandas 3 #56642

New issue
New issue
Open
Open
ENH: Need new semantics for selecting parquet engine in Pandas 3#56642
Labels
BlockedClosing CandidateMay be closeable, needs more eyeballsDeprecateFunctionality to remove in pandasIO Parquetparquet, feather
@davetapley

Description

@davetapley
davetapley
opened on Dec 27, 2023

Feature Type

  • Adding new functionality to pandas

  • Changing existing functionality in pandas

  • Removing existing functionality in pandas

Problem Description

This isn't a problem right now, but I just wanted to call it out ahead of 3.0:

This behavior:

pandas/pandas/io/parquet.py

Lines 433 to 437 in 8b77271

engine : {{'auto', 'pyarrow', 'fastparquet'}}, default 'auto'
Parquet library to use. If 'auto', then the option
``io.parquet.engine`` is used. The default ``io.parquet.engine``
behavior is to try 'pyarrow', falling back to 'fastparquet' if
'pyarrow' is unavailable.

Won't really make sense in 3.0 and onwards, because:

pandas/doc/source/whatsnew/v2.2.0.rst

Line 87 in 8b77271

- PyArrow will become a required dependency with pandas 3.0 to accommodate this change.

Feature Description

I guess just always use pyarrow unless explicitly told to use fastparquet?

Alternative Solutions

N/A

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    BlockedClosing CandidateMay be closeable, needs more eyeballsDeprecateFunctionality to remove in pandasIO Parquetparquet, feather

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions