Skip to content

Conversation

@yhuai
Copy link
Contributor

@yhuai yhuai commented Jun 23, 2015

https://issues.apache.org/jira/browse/SPARK-8578

It is not very safe to use a custom output committer when append data to an existing dir. This changes adds the logic to check if we are appending data, and if so, we use the output committer associated with the file output format.

@yhuai
Copy link
Contributor Author

yhuai commented Jun 23, 2015

Will create a PR for 1.4 branch.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"save" => "safe"

@liancheng
Copy link
Contributor

LGTM except for several minor stuff.

@yhuai
Copy link
Contributor Author

yhuai commented Jun 24, 2015

test this please.

@SparkQA
Copy link

SparkQA commented Jun 24, 2015

Test build #35607 has finished for PR 6964 at commit d2e9cce.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • s"Using output committer class $
    • logInfo(s"Using user defined output committer class $
    • logInfo(s"Using output committer class $

@SparkQA
Copy link

SparkQA commented Jun 24, 2015

Test build #35617 has finished for PR 6964 at commit ad469df.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • s"Using output committer class $
    • logInfo(s"Using user defined output committer class $
    • s"Using output committer class $

@yhuai
Copy link
Contributor Author

yhuai commented Jun 24, 2015

test this please

@chenghao-intel
Copy link
Contributor

Typo in the PR title, should be [SPARK-8578]

@yhuai yhuai changed the title [SPSARK-8578] [SQL] Should ignore user defined output committer when appending data [SPARK-8578] [SQL] Should ignore user defined output committer when appending data Jun 24, 2015
@yhuai
Copy link
Contributor Author

yhuai commented Jun 24, 2015

Changed. Thanks!

@SparkQA
Copy link

SparkQA commented Jun 24, 2015

Test build #35625 has finished for PR 6964 at commit ad469df.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • s"Using output committer class $
    • logInfo(s"Using user defined output committer class $
    • s"Using output committer class $

@SparkQA
Copy link

SparkQA commented Jun 24, 2015

Test build #35639 has finished for PR 6964 at commit 43544c4.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):
    • s"Using output committer class $
    • logInfo(s"Using user defined output committer class $
    • s"Using output committer class $

@yhuai
Copy link
Contributor Author

yhuai commented Jun 24, 2015

Thanks for reviewing it! I am merging it to master.

@asfgit asfgit closed this in bba6699 Jun 24, 2015
asfgit pushed a commit that referenced this pull request Jun 24, 2015
…ppending data (branch 1.4)

This is #6964 for branch 1.4.

Author: Yin Huai <[email protected]>

Closes #6966 from yhuai/SPARK-8578-branch-1.4 and squashes the following commits:

9c3947b [Yin Huai] Do not use a custom output commiter when appendiing data.
nemccarthy pushed a commit to nemccarthy/spark that referenced this pull request Jun 25, 2015
…ppending data (branch 1.4)

This is apache#6964 for branch 1.4.

Author: Yin Huai <[email protected]>

Closes apache#6966 from yhuai/SPARK-8578-branch-1.4 and squashes the following commits:

9c3947b [Yin Huai] Do not use a custom output commiter when appendiing data.
@liancheng
Copy link
Contributor

@JoshRosen It's a little bit weird that this PR still appears in the PR dashboard even it's merged and closed.

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