-
v0.7.0-beta.066ad166f · ·
v0.7.0-beta.0 Release CHANGELOG * This beta release exists to test the XCOM push of dbt artifacts
-
v0.5.0a5e89d96 · ·
v0.5.0 Release The minor version bump is because operators no longer have a task attribute but a command attribute. This makes more sense since dbt also calls its operations as commands, but it represents a breaking change. Moreover, the operator now pushes the results of a dbt run even when a dbt command fails, to provide better context for alerting and error handling. With this release it seems the operator has reached or is close to a state of feature completion. Future patches may focus on fixing bugs, increasing test coverage, and eventually maintaining new dbt versions. The only exception is logging: I'd like to figure out dbt logging so that we can direct dbt's logger to the Airflow stream, instead of to a file that we later read.
-
v0.4.27a1ffbbe · ·
v0.4.2 Release This version includes an import fix for DbtSeedOperator when running with do_xcom_push=True. The command was returning an agate.table.Table object that is not JSON serializable, so the task would fail. We now produce a dictionary of column names and types instea of the table object. There is also some minor clean up work done.
-
v0.4.1bea2de5f · ·
v0.4.1 Release This version includes full support for JSON cross-communication (XCOM) between Airflow tasks. JSON is the default backend, but custom XCOM backend support may be added in subclasses. The way it works is by turning dbt's RunExecutionResult objects into Python dictionaries, using dataclass.isdict, and casting non JSON-serializable types into strings.
-
v0.3.5371c2a76 · ·
v0.3.5 Release This version includes a better attempt at proper logging handling of dbt's STDOUT logging: by changing the output of the dbt logger's stream handler to a file, we can later read that file and use the Airflow task's logger to log the lines. This should make the log lines appear in the Airflow UI at least for version 1.10. >= 2.0 versions need to be tested.
-
v0.3.47af5e199 · ·
v0.3.4 Release Make returning from operator optional via the xcom_push argument (False by default). This was causing issues as dbt sometimes returns dataclasses which were not serializable. When that's the case we attempt to cast them to dicts before returning. dbt logging does not work properly in MWAA: the logs get written to the worker log but not to the task log, which means they cannot be visualized via the UI. I've attempted to fix this by setting Airflow logger's handlers to dbt on initializing a dbt operator.