chore(deps): update dependency pyarrow to v23

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
pyarrow	==21.0.0 → ==23.0.0
pyarrow	==20.0.0 → ==23.0.0
pyarrow	==17.0.0 → ==23.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on updating the pyarrow dependency to its latest stable version, 23.0.0, across several requirements.txt files within the bigquery and bigquery_storage directories. This ensures that the projects leverage the most recent features, performance improvements, and bug fixes provided by the pyarrow library, maintaining dependency hygiene and compatibility with modern Python environments.

Highlights

• PyArrow Dependency Update: The pyarrow dependency has been updated to version 23.0.0 across multiple requirements.txt files.
• Version Consolidation: In bigquery/bqml/requirements.txt and bigquery/pandas-gbq-migration/requirements.txt, pyarrow is now consistently set to 23.0.0 for all specified Python versions (<=3.8 and >3.9).
• Targeted Update: For bigquery_storage/to_dataframe/requirements.txt, the pyarrow version for python_version >= '3.9' has been updated to 23.0.0, while older Python versions retain their existing pyarrow specifications.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the pyarrow dependency to version 23.0.0 across multiple requirements.txt files. The changes are generally good, but I've identified an opportunity to improve maintainability by consolidating redundant dependency specifications in two of the files. My suggestions aim to make the dependency lists more concise and easier to manage.

[gemini-code-assist]

For conciseness and to avoid repetition, you can combine these two pyarrow dependency specifications into a single line using an or condition in the environment marker.

pyarrow==23.0.0; python_version <= '3.8' or python_version > '3.9'

[gemini-code-assist]

These two lines for pyarrow can be consolidated into a single line. This improves readability and makes the dependency list easier to manage.

pyarrow==23.0.0; python_version <= '3.8' or python_version > '3.9'