uranusjr commented on code in PR #68517:
URL: https://github.com/apache/airflow/pull/68517#discussion_r4204091565
##########
airflow-core/docs/authoring-and-scheduling/asset-scheduling.rst:
##########
@@ -75,18 +75,20 @@ You can find a listing of the relationships between assets
and Dags in the :ref:
Multiple assets
-----------------
-Because the ``schedule`` parameter is a list, Dags can require multiple
assets. Airflow schedules a Dag after **all** assets
-the Dag consumes have been updated at least once since the last time the Dag
ran:
+Dags can require multiple assets by combining them with ``&``; such Dags batch
events by default.
+Airflow schedules a Dag after **all** assets the Dag consumes have been
updated at least
+once since the last time the Dag ran:
.. code-block:: python
+ from airflow.sdk import AssetTriggeredTimetable
+
with DAG(
dag_id="multiple_assets_example",
- schedule=[
- example_asset_1,
- example_asset_2,
- example_asset_3,
- ],
+ schedule=AssetTriggeredTimetable(
+ assets=example_asset_1 & example_asset_2 & example_asset_3,
+ batch_asset_events=True,
+ ),
Review Comment:
`&` conditions already default to batching, these examples shouldn’t need to
be rewritten?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
