kaxil commented on a change in pull request #10711:
URL: https://github.com/apache/airflow/pull/10711#discussion_r482927815
##########
File path: docs/dag-serialization.rst
##########
@@ -62,16 +69,19 @@ Add the following settings in ``airflow.cfg``:
# You can also update the following default configurations based on your
needs
min_serialized_dag_update_interval = 30
min_serialized_dag_fetch_interval = 10
+ max_num_rendered_ti_fields_per_task = 30
-* ``store_serialized_dags``: This flag decides whether to serialise DAGs and
persist them in DB.
+* ``store_serialized_dags``: This option decides whether to serialise DAGs
and persist them in DB.
If set to True, Webserver reads from DB instead of parsing DAG files
-* ``store_dag_code``: This flag decides whether to persist DAG files code in
DB.
+* ``store_dag_code``: This option decides whether to persist DAG files code
in DB.
If set to True, Webserver reads file contents from DB instead of trying to
access files in a DAG folder.
* ``min_serialized_dag_update_interval``: This flag sets the minimum
interval (in seconds) after which
the serialized DAG in DB should be updated. This helps in reducing
database write rate.
-* ``min_serialized_dag_fetch_interval``: This flag controls how often a
SerializedDAG will be re-fetched
+* ``min_serialized_dag_fetch_interval``: This option controls how often a
SerializedDAG will be re-fetched
from the DB when it's already loaded in the DagBag in the Webserver.
Setting this higher will reduce
load on the DB, but at the expense of displaying a possibly stale cached
version of the DAG.
+* ``max_num_rendered_ti_fields_per_task``: This options controls maximum
number of Rendered Task Instance
Review comment:
```suggestion
* ``max_num_rendered_ti_fields_per_task``: This option controls maximum
number of Rendered Task Instance
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
