Github user rekhajoshm commented on the pull request:
https://github.com/apache/spark/pull/7253#issuecomment-120191046
@vanzin ok. With descending endtime, what i am thinking is -
As we both agree in case 4, when a1 is incomplete(end time unknown, but
optimistically will occur, definitely later than a2), and a2 is complete we
show a2 first(which implies we are showing one with fastest end time), but if
both complete soon we flip the order.Showing now a1 first and then a2, because
now both are completed we sort descending end time.This is inconsistent.
For me as a user, I find that in some remote brain cell a bit flippant when
that flip happens :-)
But will do as you suggest @vanzin .thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
