jason810496 commented on issue #72876:
URL: https://github.com/apache/airflow/issues/72876#issuecomment-5616709880

   The simplest way to fix it with correct semantics I imagine is introducing a 
optional unique constraint idempotent key column on DagRun table. Or having a 
dedicated table if there's other routes that need the same semantics but this 
also means we will need to design the lifecycle and retention.
   
   So probably just keep it simple as new column on DagRun.


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