You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installing the Flink backend should be done with pip install ibis-framework apache-flink (or pip install ibis-framework 'apache-flink>=1.18'?). This differs from the installation instructions for every other backend, so probably needs to be overridden in the overlay.
For the pip install question, was this the issue of the beamer pin leaving us with an older version of pyarrow?
Because that only impacts ibis developers and users of the flink backend and we've dealt with pyarrow pins before (mostly with snowflake)
@gforsyth Yes; in order to avoid that, we've not added apache-flink to the "flink" extra requirements.
I think @cpcloud also mentioned the Snowflake example (recently resolved), and that we could find a way to include the extra while not downgrading PyArrow for every other backend during development/testing.
I'm flexible on this; if you all think it's easy/convenient to override the PyArrow pin for dev/CI, it would obviously be nice to be able to just do pip install ibis-framework[flink]. That being said, pip install ibis-framework apache-flink isn't all that ugly, either.
Please describe the issue
Installing the Flink backend should be done with
pip install ibis-framework apache-flink
(orpip install ibis-framework 'apache-flink>=1.18'
?). This differs from the installation instructions for every other backend, so probably needs to be overridden in the overlay.Also, we don't yet have a path to supporting installation with
conda/mamba
, pending Flink being made available viaconda-forge
.Code of Conduct
The text was updated successfully, but these errors were encountered: