-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Switch XCom implementation to use run_id #20975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
3d93fe2 to
dbc24bb
Compare
This comment has been minimized.
This comment has been minimized.
|
Nice, MySQL is now failing on the same places as Postgres. SQLite fails just a few more (it’s complaining about unique constraint violation not happening on other backends, not sure why). MSSQL is complaining about the |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
df2133a to
3e28291
Compare
This comment has been minimized.
This comment has been minimized.
60e419d to
54e6cb7
Compare
|
Marking this as ready since all failing tests are from main. This does not break anything. |
|
Static checks are fixed in main. |
17e3d7e to
9517a3e
Compare
This works around MySQL's index size limit.
The pk that makes the most sense, (key, dag_id, task_id, run_id), goes over MySQL's index length limit, so we need so find an alternative way to enforce uniqueness. DagRun.id replaces (dag_id, run_id) and allows us to stay under the limit.
I don't know why it worked previously, but I know it works now.
This allows the query to make use of SQLAlchemy's keyword quoting logic so we can correctly handle quote differences between different database implementations (I'm looking at you, MySQL and Microsoft SQL Server).
This seems to be needed now.
9517a3e to
69a5766
Compare
|
This change lead to failing migrations because I had several DAGs with the same task name, but different DAG names. Should be xcom results be identified by DAG name as well? |
Real-world tests needed.