uranusjr commented on issue #28868: URL: https://github.com/apache/airflow/issues/28868#issuecomment-1379867945
The real problem is not actually the run ID, but the logical date (execution date), which also has a unique constraint, and can be identical if you schedule too fast. Even if the run ID duplication is fixed, you still can’t schedule multiple runs under the same logical date. So that’s the thing you must explicitly pass to `expand` (or `expand_kwargs`) if you want to use dynamic task mapping. -- 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]
