-
Notifications
You must be signed in to change notification settings - Fork 85
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
Compiling from source fails to find pyarrow #314
Comments
This build works:
But I dont know if the software will work as a commented in the linked issue has then following comment:
in reference to symlinking. This also means we cant define |
The fix that was mentioned in the previous issue, is likely the one in this doc https://arrow.apache.org/docs/python/extending.html#building-extensions-against-pypi-wheels and referenced in this comment #276 (comment). I think its a bad call from pyarrow to ask consumers to modify the installation. |
The documentation you linked was helpful for me. I am now able to get turbodbc up and running without conda for the first time. I am installing pyarrow in a separate RUN command with some other dependencies, then I have a line which runs the create_library_symlinks() command. Finally, the rest of my requirements (including turbodbc and airflow-providers-odbc) are installed.
|
Well, the build worked but then turbodbc was not able to find pyarrow during actual tasks. Both libraries are installed in the same environment. I will try @pecigonzalo's approach with symlinks I know this works with conda, but I want to move towards using the official apache/airflow image which does not use conda. The only failure is turbodbc right now. |
Negative. I ended up installing with mamba instead and used a package called conda-pack to avoid having conda installed in my final image.
My final image copies my venv folder which results in a working pyarrow without anaconda installed .
I am still hoping for the day when I can pip install everything since a chunk of my most important libraries are not on conda at all. |
@DevangB9 I recently was able to solve this issue and posted it in this comment. |
As already reflected in #276 compiling from source fails to find
pyarrow
outside ofconda
.This is using
pyarrow
installation from wheels.Reproduce in
I dont understand why #276 was closed as many users are reporting the exact same issue. The issue is likely due to
pyarrow
.so
files being suffixed with.300
for version3.0.0
and so on.The following comment (which links to the actual comments) compiling from source is mentioned as symlinking the names will not work, but its not clear what needs to be compiled.
Sample error output:
The text was updated successfully, but these errors were encountered: