You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/06/07 13:54:46 UTC
[GitHub] [airflow] kaxil opened a new issue #16304: Add data_interval_start and data_interval_end columns to DagRun table, and set them when creating DagRuns.
kaxil opened a new issue #16304:
URL: https://github.com/apache/airflow/issues/16304
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr edited a comment on issue #16304: Add data_interval_start and data_interval_end columns to DagRun table, and set them when creating DagRuns.
Posted by GitBox <gi...@apache.org>.
uranusjr edited a comment on issue #16304:
URL: https://github.com/apache/airflow/issues/16304#issuecomment-857687085
What should we set the values to for DAGs with `schedule_interval` either `None` or `"@once"`? They don’t really have a data interval so both `(execution_date, execution_date)` and `(execution_date, None)` seem sensible to me.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr closed issue #16304: Add data_interval_start and data_interval_end columns to DagRun table, and set them when creating DagRuns.
Posted by GitBox <gi...@apache.org>.
uranusjr closed issue #16304:
URL: https://github.com/apache/airflow/issues/16304
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #16304: Add data_interval_start and data_interval_end columns to DagRun table, and set them when creating DagRuns.
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #16304:
URL: https://github.com/apache/airflow/issues/16304#issuecomment-857687085
What should we set the values to for DAGs with `schedule_interval` either `None` or `"@once"`? They don’t really have a data interval so both `(execution_date, execution_date)` and `(execution_date, None)` feels sensible to me.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #16304: Add data_interval_start and data_interval_end columns to DagRun table, and set them when creating DagRuns.
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #16304:
URL: https://github.com/apache/airflow/issues/16304#issuecomment-857826651
Currently working on this; I’m using the `(execution_date, execution_date)` value since it allows making the columns non-nullable. But can `DagRun.execution_date` be `None` to begin with? If it can, those new fields need to be nullable as well anyway.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org