Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[SPARK-4380] Log more precise number of bytes spilled (1.1) #3355

Closed
wants to merge 1 commit into from
Closed

[SPARK-4380] Log more precise number of bytes spilled (1.1) #3355

wants to merge 1 commit into from
+6 −4

Conversation

andrewor14
Copy link
Contributor

This is the branch-1.1 version of #3243.

@SparkQA
Copy link

SparkQA commented Nov 19, 2014

QA tests have started for PR 3355 at commit 36ec152.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Nov 19, 2014

QA tests have finished for PR 3355 at commit 36ec152.

  • This patch passes unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/23581/
Test PASSed.

@andrewor14
Copy link
Contributor Author

Alright I'm merging this into 1.1 thanks.

asfgit pushed a commit that referenced this pull request Nov 19, 2014
[SPARK-4380] Log more precise number of bytes spilled (1.1)
e22a759 
This is the branch-1.1 version of #3243.

Author: Andrew Or <andrew@databricks.com>

Closes #3355 from andrewor14/spill-log-bytes-1.1 and squashes the following commits:

36ec152 [Andrew Or] Log more precise representation of bytes in spilling code
@andrewor14 andrewor14 closed this Nov 19, 2014
@andrewor14 andrewor14 deleted the spill-log-bytes-1.1 branch November 19, 2014 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@andrewor14 @SparkQA @AmplabJenkins