uranusjr commented on code in PR #48379: URL: https://github.com/apache/airflow/pull/48379#discussion_r2013558498
########## airflow-core/docs/administration-and-deployment/lineage.rst: ########## @@ -71,11 +71,6 @@ for the downstream task. In the example DAG task ``run_this`` (``task_id=run_me_first``) is a BashOperator that takes 3 inlets: ``CAT1``, ``CAT2``, ``CAT3``, that are generated from a list. Note that ``data_interval_start`` is a templated field and will be rendered when the task is running. -.. note:: Behind the scenes Airflow prepares the lineage metadata as part of the ``pre_execute`` method of a task. When the task - has finished execution ``post_execute`` is called and lineage metadata is pushed into XCOM. Thus if you are creating - your own operators that override this method make sure to decorate your method with ``prepare_lineage`` and ``apply_lineage`` - respectively. Review Comment: The hooks are now unconditionally called in the sdk, so the decorators are no longer needed. -- 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]
