First, congratulations to the contributors on getting 1.8 out and especially to Bolke for the Herculean effort!
I noticed one issue in 1.8 that we didn't see in the previous Airflow version that we've been running in production and staging. I've filed Jira https://issues.apache.org/jira/browse/AIRFLOW-1011 with a test DAG and some screenshots. Here's the description from the Jira: ------------------------------------------------------------------------------------------ Before 1.8, results for tasks executed as a subdag were written as rows to task_instances. In Airflow 1.8 only rows for tasks inside the top-level DAG (non-subdag tasks) seem to get written to the database. This results in being unable to check the status of task instances inside the subdag from the UI, check the logs for those task instances from the UI, etc. Attached is a simple test DAG that exhibits the issue along with screenshots showing the UI differences between v1.8 and v1.7.1.3. Note that if the DAG is run via backfill from command line (e.g. "airflow backfill Test_SubDAG -s 2017-03-18 -e 2017-03-18") the task instances show up successfully. Also, we're using CeleryExecutor and not specifying a different executor for our subdags. ------------------------------------------------------------------------------------------ If I can provide more info, let me know. Thanks, -Joe
