Page History

...

There is still a unique constraint on run_id.  Currently it is generated deterministically from logical date plus run type.  What should we do for runs with no logical date?  How can we support the use case with many runs triggered in close succession such that perhaps even utcnow()  would collide.  What shall we do?

Resolution of questions

Here will be where I work out the consensus view based on feedback.  This will be amended as we go.

• Manual runs (question 1)
  • behavior in legacy UI and connexion API will be unchanged
  • in new REST API, when triggering a run logical date will be required field and may be null
  • in new UI, when triggering a run, it will be default None but you can select a date with date picker
    • if you try to trigger a date that already exists, you will not be able to.  you can use backfill to rerun a historical date
  • TriggerDagRunOperator will have a default of None for logical date
  • CLI dag run trigger will be default none, but you can add a logical date if you like.
• Asset triggered
  • no logical date
  • data interval?