Skip to content

Conversation

@nongli
Copy link
Contributor

@nongli nongli commented Dec 4, 2015

When the spillable sort iterator was spilled, it was mistakenly keeping
the last page in memory rather than the current page. This causes the
current record to get corrupted.

…ferenced.

When the spillable sort iterator was spilled, it was mistakenly keeping
the last page in memory rather than the current page. This causes the
current record to get corrupted.
@davies
Copy link
Contributor

davies commented Dec 4, 2015

LGTM

@SparkQA
Copy link

SparkQA commented Dec 4, 2015

Test build #47189 has finished for PR 10142 at commit 7ea40a7.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):\n * class SparkPlanInfo(\n * class SQLMetricInfo(\n * case class SparkListenerSQLExecutionStart(\n * case class SparkListenerSQLExecutionEnd(executionId: Long, time: Long)\n

@yhuai
Copy link
Contributor

yhuai commented Dec 4, 2015

test this please

@SparkQA
Copy link

SparkQA commented Dec 4, 2015

Test build #47200 has finished for PR 10142 at commit 7ea40a7.

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

@davies
Copy link
Contributor

davies commented Dec 4, 2015

Merged into master and 1.6 branch, thanks!

@asfgit asfgit closed this in 95296d9 Dec 4, 2015
asfgit pushed a commit that referenced this pull request Dec 4, 2015
…ferenced

When the spillable sort iterator was spilled, it was mistakenly keeping
the last page in memory rather than the current page. This causes the
current record to get corrupted.

Author: Nong <[email protected]>

Closes #10142 from nongli/spark-12089.

(cherry picked from commit 95296d9)
Signed-off-by: Davies Liu <[email protected]>
@nongli nongli deleted the spark-12089 branch December 10, 2015 05:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants