Resending with links since the apache mail server does not allow emails larger than ~1MB.
-s On Mon, Jun 27, 2016 at 7:13 PM, siddharth anand <[email protected]> wrote: > I found this to also be a little jarring at first, but the functionality > is an arguable improvement. > > For the benefit of others on this list, it's worth providing UI snapshots. > > Here is a before and after screen shot of what I believe the reporter is > referring to : > > *Before (1.6.2)* > > https://www.dropbox.com/s/qthe4g3ptqldkv1/Screenshot%202016-06-27%2019.01.15.png?dl=0 > > > *After (1.71.3)* > > https://www.dropbox.com/s/szuw6fv1y68fscu/Screenshot%202016-06-27%2019.00.53.png?dl=0 > > > The "*Statuses*" column has been changed to "*Recent Statuses*" between > 1.6.2 and 1.7.1.x > > Instead of showing task statuses from the beginning of time for a DAG, it > only shows "recent statuses". If you hover over the information tool tip, > you will see the following : > > https://www.dropbox.com/s/a1534i3r8z3jkd7/Screenshot%202016-06-27%2019.04.26.png?dl=0 > > > I actually find this to be pretty useful. What's missing is actually an > other column for dag run statuses (at a glance). It's pretty useless for me > to see a number like 1000 successful task runs in the old "Successes" > column. It's more useful to me as it stands now with task statuses for the > currently active or previous dag run. I would also wish to see a column for > dag run statuses (counts of dags in success, failed, etc.. states). > Together, those 2 columns would provide a complete and useful picture. > > -s > > On Mon, Jun 27, 2016 at 11:39 AM, daniel williams < > [email protected]> wrote: > >> Chris, That is exactly right. We have run many instances of a specific >> DAG >> on an hourly schedule where in the airflow db it reports an accurate >> number >> but the Web UI shows 12 successes consistently. >> >> On Mon, Jun 27, 2016 at 10:37 AM, Chris Riccomini <[email protected]> >> wrote: >> >> > Hey Daniel, >> > >> > What do you mean by DAG status? Are you referring to a DAG run's state >> > (success, failed, etc), the toggle on/off switch, the last time the DAG >> was >> > refreshed, or something else? >> > >> > Cheers, >> > Chris >> > >> > On Fri, Jun 24, 2016 at 12:10 PM, daniel williams < >> > [email protected] >> > > wrote: >> > >> > > Hi, >> > > >> > > I was running a 1.7 release candidate and noticed that the DAG status >> for >> > > some reason came out of sync with the database. In order to resolve >> > this I >> > > upgraded to 1.7.1.3 and the same condition is occurring. Is there a >> > > configuration in the DB or the airflow.cfg that I should be aware of >> that >> > > could be causing this? I've restarted the webserver and scheduler >> many >> > > times with no success. >> > > >> > > Any insights appreciated. Thanks. >> > > >> > > dan >> > > >> > >> >> >> >> -- >> -dan >> > >
