ashb commented on PR #58741: URL: https://github.com/apache/airflow/pull/58741#issuecomment-3583254921
> I’ve opened the PR, but there are still a few points to discuss. It seems that the ideal approach would be to generate an external ID (for example, a UUID) inside the scheduler (or executor) and pass this ID to the actual task. However, this approach has a limitation: not all executors may support it. If this is the desired solution, I can proceed with the implementation. Airflow 3 already does exactly this. the `ti.id` is a UUID that uniquely identifies the try (not just the TI like in 2.x times) -- 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]
