Background: the Airflow Postgres connection uses the schema parameter to specify the database (see: https://airflow.apache.org/docs/apache-airflow-providers-postgres/stable/connections/postgres.html). This lead to a double use of the self.schema attribute in the operator in case of using it with postgres, both for the database and the schema which in effect meant if those values were not the same it did not work.
This PR changes the postgres connection to use the schema parameter defined in the connection itself as the database name and use the schema parameter of the operator (or a schema.table notation for the data_asset parameter) as the schema within the GX context.
Background: the Airflow Postgres connection uses the
schemaparameter to specify the database (see: https://airflow.apache.org/docs/apache-airflow-providers-postgres/stable/connections/postgres.html). This lead to a double use of theself.schemaattribute in the operator in case of using it with postgres, both for the database and the schema which in effect meant if those values were not the same it did not work.This PR changes the postgres connection to use the
schemaparameter defined in the connection itself as the database name and use theschemaparameter of the operator (or aschema.tablenotation for thedata_assetparameter) as the schema within the GX context.