GH-47989: [Python][Docs] Add filters_to_expression to Parquet API reference

[Sansfear87]

Fixes #47989

Adds filters_to_expression to the Parquet autosummary section in formats.rst.
Documentation-only change.

• GitHub Issue: [Python][Docs] Add pyarrow.parquet.filters_to_expression to API reference docs #47989

[github-actions]

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - Contributing Overview

[Sansfear87]

Hi, I added filters_to_expression to the Parquet autosummary in formats.rst (Fixes #47989). This is a documentation-only change. Let me know if any adjustments are needed. Thanks!

[AlenkaF]

Thanks for the contribution @Sansfear87!
Minor suggestion: when opening a PR it is advisable to update the existing GitHub Pull Request template and to check our contributing guidelines here: https://arrow.apache.org/docs/developers/overview.html#pull-request-and-review (PR title).

I have run the CI and will run the docs preview job, just to check the change renders correctly.

[AlenkaF]

@github-actions crossbow submit preview-docs

[github-actions]

Revision: 285c36d

Submitted crossbow builds: ursacomputing/crossbow @ actions-f6bd5325ed

Task	Status
preview-docs

[Sansfear87]

Thanks for the contribution @Sansfear87! Minor suggestion: when opening a PR it is advisable to update the existing GitHub Pull Request template and to check our contributing guidelines here: https://arrow.apache.org/docs/developers/overview.html#pull-request-and-review (PR title).

I have run the CI and will run the docs preview job, just to check the change renders correctly.

Thank you for the guidance! I’ll make sure to follow the PR template and title formatting in future PRs.

[AlenkaF]

Thanks for the contribution @Sansfear87, the change looks correct:
https://s3.amazonaws.com/arrow-data/pr_docs/48233/python/api/formats.html#parquet-files

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit c3c56e1.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 1 possible false positive for unstable benchmarks that are known to sometimes produce them.