Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: google-cloud-bigquery cannot be imported when pyarrow 2.0 or earlier is installed #933

Closed
tswast opened this issue Sep 1, 2021 · 1 comment · Fixed by #934
Closed
Assignees
Labels
api: bigquery Issues related to the googleapis/python-bigquery API. priority: p0 Highest priority. Critical issue. P0 implies highest priority. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@tswast
Copy link
Contributor

tswast commented Sep 1, 2021

Requiring pyarrow >=3.0 is causing the Apache Beam and TFX teams some issues (internal issue 197861846). We should allow older versions of pyarrow to be used for those features where it can be (and re-add any relevant warnings when it can't)

@product-auto-label product-auto-label bot added the api: bigquery Issues related to the googleapis/python-bigquery API. label Sep 1, 2021
@tswast
Copy link
Contributor Author

tswast commented Sep 1, 2021

Alternatively, we should guard against old versions of pyarrow so that we don't get import errors for the whole package if an old version of pyarrow happens to be installed.

@tswast tswast added priority: p0 Highest priority. Critical issue. P0 implies highest priority. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Sep 1, 2021
@tswast tswast self-assigned this Sep 1, 2021
@tswast tswast changed the title expand allowed pyarrow dependencies back to >=1.0 in google-cloud-bigquery v2.x bug: google-cloud-bigquery cannot be imported when pyarrow 2.0 or earlier is installed Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the googleapis/python-bigquery API. priority: p0 Highest priority. Critical issue. P0 implies highest priority. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant