Sorry, here are two more PRs I guess should be closed.
10052 dereksabryfb - This one is suggested by Sean and Herman to close
10356 somideshmukh - This has not been confirmed by a committer yet but
I tested this and it seems not an issue.
Thanks.
2016-05-07 2:47 GMT+09:00 Sean Owen :
> Sk
Skimmed these as a one-off exercise, and I suggest ...
Leave open for now
7739 mgrover
10701 nraychaudhuri
9920 jliwork
9936 Lewuathe
10052 dereksabryfb
10125 kevinyu98
10466 hhbyyh
10995 tedyu
10887 blbradley
11005 huaxingao
11129 AtkinsChang
11610 iyounus
11729 mbaddar1
11980 koertkuipers
12075
Alex has built tooling for this btw:
https://github.com/databricks/spark-pr-dashboard/pull/71
On Fri, May 6, 2016 at 12:15 PM Ted Yu wrote:
> PR #10572 was listed twice.
>
> In the future, is it possible to include the contributor's handle beside
> the PR number so that people can easily recogni
PR #10572 was listed twice.
In the future, is it possible to include the contributor's handle beside
the PR number so that people can easily recognize their own PR ?
Thanks
On Fri, May 6, 2016 at 8:45 AM, Hyukjin Kwon wrote:
> Hi all,
>
>
> This was similar with the proposal of closing PRs bef
Hi all,
This was similar with the proposal of closing PRs before I asked.
I think the PRs suggested to be closed below are closable but not very sure
of PRs apparently abandoned by its author at least for a month.
I remember the discussion about auto-closing PR before. So, I included the
PRs as
Hi,
While reviewing TaskSchedulerImpl I've noticed that rootPool is
created and initialized in TaskSchedulerImpl#initialize [1], but seems
legit to do it as part of TaskSchedulerImpl's instantiation.
What is the reason for creating and initializing rootPool late in
TaskSchedulerImpl's lifecycle?