This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new d8b730a Fix typo in docs (#22024)
d8b730a is described below
commit d8b730a57b8eb4e6bc408b3553b16ada2386ae8e
Author: Taeho Kim <[email protected]>
AuthorDate: Sun Mar 6 21:52:59 2022 +0900
Fix typo in docs (#22024)
---
docs/apache-airflow-providers-google/operators/cloud/dataflow.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/apache-airflow-providers-google/operators/cloud/dataflow.rst
b/docs/apache-airflow-providers-google/operators/cloud/dataflow.rst
index 2fddff9..32ac462 100644
--- a/docs/apache-airflow-providers-google/operators/cloud/dataflow.rst
+++ b/docs/apache-airflow-providers-google/operators/cloud/dataflow.rst
@@ -133,7 +133,7 @@ By default
:class:`~airflow.providers.google.cloud.operators.dataflow.DataflowCr
:class:`~airflow.providers.google.cloud.operators.dataflow.DataflowCreatePythonJobOperator`,
:class:`~airflow.providers.google.cloud.operators.dataflow.DataflowTemplatedJobStartOperator`
and
:class:`~airflow.providers.google.cloud.operators.dataflow.DataflowStartFlexTemplateOperator`
-have argument ``wait_until_finished`` set to ``None`` which cause different
behaviour depends om the type of pipeline:
+have argument ``wait_until_finished`` set to ``None`` which cause different
behaviour depends on the type of pipeline:
* for the streaming pipeline, wait for jobs to start,
* for the batch pipeline, wait for the jobs to complete.
