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
Currently, we have two ways to use Ibis, one way is to create the dataframe and execution engine abstractions on top of Ibis, and this is used by our Bigquery and trino integrations. Another way is inside FugueWorkflow we enable a function called as_ibis to convert a FugueWorkflowDataFrame in to Ibis, this is a transition between two different dags.
This feature is rarely used by users, plus, we want to hide FugueWorkflow from the top level APIs, so maintaining the second use case no longer has value. So, to make Fugue more lightweight and more focused on useful feature, we will remove this feature.
The text was updated successfully, but these errors were encountered:
This is NOT to deprecate Ibis usage from Fugue
Currently, we have two ways to use Ibis, one way is to create the dataframe and execution engine abstractions on top of Ibis, and this is used by our Bigquery and trino integrations. Another way is inside
FugueWorkflow
we enable a function calledas_ibis
to convert aFugueWorkflowDataFrame
in to Ibis, this is a transition between two different dags.This feature is rarely used by users, plus, we want to hide
FugueWorkflow
from the top level APIs, so maintaining the second use case no longer has value. So, to make Fugue more lightweight and more focused on useful feature, we will remove this feature.The text was updated successfully, but these errors were encountered: