From 2ed4b8da90c58d4fbe993a40494c92c0872c4c1a Mon Sep 17 00:00:00 2001 From: Phani Kumar Date: Fri, 20 Jan 2023 12:31:54 +0530 Subject: [PATCH] Update docs --- docs/apache-airflow-providers-dbt-cloud/operators.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/apache-airflow-providers-dbt-cloud/operators.rst b/docs/apache-airflow-providers-dbt-cloud/operators.rst index bfbf604246ea8..16d02af47e3d7 100644 --- a/docs/apache-airflow-providers-dbt-cloud/operators.rst +++ b/docs/apache-airflow-providers-dbt-cloud/operators.rst @@ -42,12 +42,15 @@ False is a good approach for long-running dbt Cloud jobs. The ``deferrable`` parameter along with ``wait_for_termination`` will control the functionality whether to poll the job status on the worker or defer using the Triggerer. -When ``wait_for_termination`` is ``True`` and ``deferrable`` is ``False,we submit the job and ``poll`` +When ``wait_for_termination`` is True and ``deferrable`` is False,we submit the job and ``poll`` for its status on the worker. This will keep the worker slot occupied till the job execution is done. -When ``wait_for_termination`` is ``True`` and ``deferrable`` is True, +When ``wait_for_termination`` is True and ``deferrable`` is True, we submit the job and ``defer`` using Triggerer. This will release the worker slot leading to savings in resource utilization while the job is running. +When ``wait_for_termination`` is False and ``deferrable`` is False, we just submit the job and +do not track the job status. + While ``schema_override`` and ``steps_override`` are explicit, optional parameters for the ``DbtCloudRunJobOperator``, custom run configurations can also be passed to the operator using the