[jira] [Updated] (AIRFLOW-1229) Make "Run Id" column clickable in Browse -> DAG Runs
[ https://issues.apache.org/jira/browse/AIRFLOW-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Cederstrand updated AIRFLOW-1229: -- Attachment: (was: dag_run_link.patch) > Make "Run Id" column clickable in Browse -> DAG Runs > > > Key: AIRFLOW-1229 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1229 > Project: Apache Airflow > Issue Type: Improvement > Components: webapp >Affects Versions: Airflow 1.8 > Environment: Python3.4 >Reporter: Erik Cederstrand > Labels: patch > Attachments: dag_run_link.patch > > > I'm triggering a lot of DAGs manually using "airflow trigger_dag my_dag > --run_id=some_unique_id". I would like to be able in the UI to browse easily > to this specific DAG run using the "some_unique_id" label. In the graph page > of the DAG, I need to know the exact execution date, which is inconvenient, > and in the Browse -> DAG Runs page I can search by "some_unique_id", but the > "Run Ids" column is not clickable. > The attached patch makes the aforementioned column clickable, so I'm sent > directly to the graph view for that specific DAG run, not the DAG in general. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AIRFLOW-1229) Make "Run Id" column clickable in Browse -> DAG Runs
[ https://issues.apache.org/jira/browse/AIRFLOW-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Cederstrand updated AIRFLOW-1229: -- Attachment: dag_run_link.patch > Make "Run Id" column clickable in Browse -> DAG Runs > > > Key: AIRFLOW-1229 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1229 > Project: Apache Airflow > Issue Type: Improvement > Components: webapp >Affects Versions: Airflow 1.8 > Environment: Python3.4 >Reporter: Erik Cederstrand > Labels: patch > Attachments: dag_run_link.patch > > > I'm triggering a lot of DAGs manually using "airflow trigger_dag my_dag > --run_id=some_unique_id". I would like to be able in the UI to browse easily > to this specific DAG run using the "some_unique_id" label. In the graph page > of the DAG, I need to know the exact execution date, which is inconvenient, > and in the Browse -> DAG Runs page I can search by "some_unique_id", but the > "Run Ids" column is not clickable. > The attached patch makes the aforementioned column clickable, so I'm sent > directly to the graph view for that specific DAG run, not the DAG in general. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AIRFLOW-1229) Make "Run Id" column clickable in Browse -> DAG Runs
[ https://issues.apache.org/jira/browse/AIRFLOW-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021055#comment-16021055 ] Erik Cederstrand commented on AIRFLOW-1229: --- Updated patch to contain execution_date in the generated link. This lets the graph show the correct DAG run instead of the latest, if there are multiple DAG runs with the same run_id. > Make "Run Id" column clickable in Browse -> DAG Runs > > > Key: AIRFLOW-1229 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1229 > Project: Apache Airflow > Issue Type: Improvement > Components: webapp >Affects Versions: Airflow 1.8 > Environment: Python3.4 >Reporter: Erik Cederstrand > Labels: patch > Attachments: dag_run_link.patch > > > I'm triggering a lot of DAGs manually using "airflow trigger_dag my_dag > --run_id=some_unique_id". I would like to be able in the UI to browse easily > to this specific DAG run using the "some_unique_id" label. In the graph page > of the DAG, I need to know the exact execution date, which is inconvenient, > and in the Browse -> DAG Runs page I can search by "some_unique_id", but the > "Run Ids" column is not clickable. > The attached patch makes the aforementioned column clickable, so I'm sent > directly to the graph view for that specific DAG run, not the DAG in general. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AIRFLOW-1240) Scheduler shuts down without num_runs=-1
Alexander Panzhin created AIRFLOW-1240: -- Summary: Scheduler shuts down without num_runs=-1 Key: AIRFLOW-1240 URL: https://issues.apache.org/jira/browse/AIRFLOW-1240 Project: Apache Airflow Issue Type: Bug Components: scheduler Affects Versions: 1.8.0 Reporter: Alexander Panzhin Without num_runs=-1 set the scheduler eventually shuts down. This happens event with run_duration set to -1. This is not in the default config in 1.8.0 , that is how this issue surfaced. I've seen this config parameter added to the default config in Git, but that is a workaround The version published in PIP has 1.8.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AIRFLOW-1241) Allow airflow test and airflow run to take arguments to pass to DAGs
Dan Davydov created AIRFLOW-1241: Summary: Allow airflow test and airflow run to take arguments to pass to DAGs Key: AIRFLOW-1241 URL: https://issues.apache.org/jira/browse/AIRFLOW-1241 Project: Apache Airflow Issue Type: Improvement Components: cli Reporter: Dan Davydov A common use case it to have conditionals in a DAG to run dev/prod code, e.g. DEV_MODE=True if DEV_MODE: hit_test_db else: hit_prod_db it would be good if you could instead pass arguments to tasks with airflow run/test e.g. airflow run some_dag some_task some_date --args foo=1 and then in the dag: something like execution_args.foo could be used (which would have value 1). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
