-
Notifications
You must be signed in to change notification settings - Fork 29k
Renamed stageIdToActiveJob to jobIdToActiveJob. #301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This data structure was misnamed and, as a result, misused.
|
Merged build triggered. |
|
Merged build started. |
|
lgtm |
1 similar comment
|
lgtm |
|
Merged build finished. All automated tests passed. |
|
All automated tests passed. |
|
good catch |
|
Thanks, merged. |
|
Yes, good catch. This isn't the first confusion/conflation of jobId and stageId within the DAGScheduler and TaskManager, so it is something to keep a sharp eye on. This renaming should make future such mistakes less likely, so it LGTMT. |
This data structure was misused and, as a result, later renamed to an incorrect name. This data structure seems to have gotten into this tangled state as a result of @henrydavidge using the stageID instead of the job Id to index into it and later @andrewor14 renaming the data structure to reflect this misunderstanding. This patch renames it and removes an incorrect indexing into it. The incorrect indexing into it meant that the code added by @henrydavidge to warn when a task size is too large (added here apache@5757993) was not always executed; this commit fixes that. Author: Kay Ousterhout <[email protected]> Closes apache#301 from kayousterhout/fixCancellation and squashes the following commits: bd3d3a4 [Kay Ousterhout] Renamed stageIdToActiveJob to jobIdToActiveJob.
* Add proxy configuration to retrofit clients. * Add logging
* Add proxy configuration to retrofit clients. * Add logging
Small upstream merge
….3.2 take bindAddress as input
This data structure was misused and, as a result, later renamed to an incorrect name.
This data structure seems to have gotten into this tangled state as a result of @henrydavidge using the stageID instead of the job Id to index into it and later @andrewor14 renaming the data structure to reflect this misunderstanding.
This patch renames it and removes an incorrect indexing into it. The incorrect indexing into it meant that the code added by @henrydavidge to warn when a task size is too large (added here 5757993) was not always executed; this commit fixes that.