potiuk commented on a change in pull request #20975:
URL: https://github.com/apache/airflow/pull/20975#discussion_r798624913



##########
File path: UPDATING.md
##########
@@ -130,6 +130,12 @@ Previously, a task’s log is dynamically rendered from the 
`[core] log_filename
 
 A new `log_template` table is introduced to solve this problem. This table is 
synchronised with the aforementioned config values every time Airflow starts, 
and a new field `log_template_id` is added to every DAG run to point to the 
format used by tasks (`NULL` indicates the first ever entry for compatibility).
 
+### XCom now define `run_id` instead of `execution_date`
+
+As a continuation to the TaskInstance-DagRun relation change started in 
Airflow 2.2, the `execution_date` columns on XCom has been removed from the 
database, and replaced by an [association 
proxy](https://docs.sqlalchemy.org/en/13/orm/extensions/associationproxy.html) 
field at the ORM level. If you access Airflow’s metadatabase directly, you 
should rewrite the implementation to use the `run_id` column instead.
+
+Note that Airflow’s metadatabase definition on both the database and ORM 
levels are considered implementation detail without strict backward 
compatibility guarantees.

Review comment:
       +1




-- 
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]


Reply via email to