From 6d3789e0425206fde0d5ac57d96bd3786e86cd48 Mon Sep 17 00:00:00 2001 From: TJaniF Date: Wed, 11 Oct 2023 13:10:19 +0200 Subject: [PATCH] change note wording --- docs/getting_started/astro.rst | 5 ++--- docs/getting_started/gcc.rst | 5 ++--- docs/getting_started/mwaa.rst | 5 ++--- docs/getting_started/open-source.rst | 5 ++--- 4 files changed, 8 insertions(+), 12 deletions(-) diff --git a/docs/getting_started/astro.rst b/docs/getting_started/astro.rst index 6188ae676..a3e2ea077 100644 --- a/docs/getting_started/astro.rst +++ b/docs/getting_started/astro.rst @@ -110,9 +110,8 @@ In your ``my_cosmos_dag.py`` file, import the ``DbtDag`` class from Cosmos and c ) .. note:: - In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``. - The recommended solution is to use the Cosmos manifest parsing method `dbt_manifest `_. - Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout `_. + In some cases, especially in larger dbt projects, you might run into a ``DagBag import timeout`` error. + This error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout `_. Start your project ~~~~~~~~~~~~~~~~~~ diff --git a/docs/getting_started/gcc.rst b/docs/getting_started/gcc.rst index cc0b8c318..53c7584f1 100644 --- a/docs/getting_started/gcc.rst +++ b/docs/getting_started/gcc.rst @@ -80,6 +80,5 @@ Make sure to rename the ```` value below to your adapter's Python .. note:: - In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``. - The recommended solution is to use the Cosmos manifest parsing method `dbt_manifest `_. - Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout `_. + In some cases, especially in larger dbt projects, you might run into a ``DagBag import timeout`` error. + This error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout `_. diff --git a/docs/getting_started/mwaa.rst b/docs/getting_started/mwaa.rst index cb742495a..49570ecc2 100644 --- a/docs/getting_started/mwaa.rst +++ b/docs/getting_started/mwaa.rst @@ -114,6 +114,5 @@ In your ``my_cosmos_dag.py`` file, import the ``DbtDag`` class from Cosmos and c .. note:: - In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``. - The recommended solution is to use the Cosmos manifest parsing method `dbt_manifest `_. - Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout `_. + In some cases, especially in larger dbt projects, you might run into a ``DagBag import timeout`` error. + This error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout `_. diff --git a/docs/getting_started/open-source.rst b/docs/getting_started/open-source.rst index a560929e1..043a454e9 100644 --- a/docs/getting_started/open-source.rst +++ b/docs/getting_started/open-source.rst @@ -66,6 +66,5 @@ For example, if you wanted to put your dbt project in the ``/usr/local/airflow/d .. note:: - In some cases, especially in projects containing a large number of DAGs, you might run into an error saying ``<> is not a valid ResourceType``. - The recommended solution is to use the Cosmos manifest parsing method `dbt_manifest `_. - Alternatively, the error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout `_. + In some cases, especially in larger dbt projects, you might run into a ``DagBag import timeout`` error. + This error can be resolved by increasing the value of the Airflow configuration `core.dagbag_import_timeout `_.