Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

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

Copy link
Copy link
Open
@davetapley

Description

@davetapley
Issue body actions

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:

- 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

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.