GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/12229
[SPARK-10063][SQL] Remove DirectParquetOutputCommitter
## What changes were proposed in this pull request?
This patch removes DirectParquetOutputCommitter. This was initially created
by Databricks as a faster way to write Parquet data to S3. However, given how
the underlying S3 Hadoop implementation works, this committer only works when
there are no failures. If there are multiple attempts of the same task (e.g.
speculation or task failures or node failures), the output data can be
corrupted. I don't think this performance optimization outweighs the
correctness issue.
## How was this patch tested?
Removed the related tests also.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark SPARK-10063
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/12229.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #12229
----
commit 8719c262f48fa0f04c991dd5a74814ed7c9d5d93
Author: Reynold Xin <[email protected]>
Date: 2016-04-07T04:34:35Z
[SPARK-10063][SQL] Remove DirectParquetOutputCommitter
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
