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
Describe the bug
Integrate using the airflow plugin v2 and then, TrinoOperator to run a query and see that the task flow and dataset are opened.
However, the dataset was linked to presto instead of trino, so it was being captured as a different dataset than the trino dataset I had linked to.
OL_SCHEME_TWEAKS seems to change trino to presto, but why is it like this?
I am having a problem with dataset separation when writing trino ingestion together.
Is it not possible to make the dataset platform of airflow Trino Operator come out as trino in order to use trino ingestion together?
To Reproduce
Steps to reproduce the behavior:
airflow plugin v2 integration
use TrinoOperator
inlet/outlet dataset comes out as presto
Expected behavior
I want the platform of the TrinoOperator to come out as trino.
The text was updated successfully, but these errors were encountered:
Describe the bug
Integrate using the airflow plugin v2 and then, TrinoOperator to run a query and see that the task flow and dataset are opened.
However, the dataset was linked to presto instead of trino, so it was being captured as a different dataset than the trino dataset I had linked to.
OL_SCHEME_TWEAKS seems to change trino to presto, but why is it like this?
I am having a problem with dataset separation when writing trino ingestion together.
Is it not possible to make the dataset platform of airflow Trino Operator come out as trino in order to use trino ingestion together?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I want the platform of the TrinoOperator to come out as trino.
The text was updated successfully, but these errors were encountered: