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
Pyarrow library not detected, so QueryJob.to_dataframe()
doesn't work
#376
Comments
@robertlacok This error is related to For me it's working fine, following are my environment details:
|
Hey, @HemangChothani thanks for taking a look. I understand that's what the error says, but installing pyarrow doesn't resolve this. I can see |
@robertlacok Could please try to restart the kernel and try to import again? |
I see, so that helped, thanks. Curious though:
But if |
I see, thanks. I'll change the tooltip for our bigquery integration to suggest installing
|
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":
If you are still having issues, please be sure to include as much information as possible:
Environment details
python --version
tried on3.7.9
and3.8.1
pip --version
20.2.3
google-cloud-bigquery
version:pip show google-cloud-bigquery
2.3.1
Steps to reproduce
google-cloud-bigquery==2.3.1
to_dataframe()
function on QueryJob, it throws an error that pyarrow library is not installedpyarrow
withpip install pyarrow
does not resolve the problemSome extra info:
google-cloud-bigquery==2.1.0
onto a fresh system works finepip install --upgrade google-cloud-bigquery==2.1.0
after having2.3.1
installed doesn't resolve the problem.Code example
I documented the steps here:
https://deepnote.com/publish/0c5c5788-aae0-407f-9aec-3716e3a62a1b
Stack trace
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
The text was updated successfully, but these errors were encountered: