From bca86bd289137dade85c125d37a64b29035b6086 Mon Sep 17 00:00:00 2001 From: Felipe Lopes Date: Tue, 30 Jul 2019 12:47:55 +0100 Subject: [PATCH] HADOOP-16469. Update committers.md Contributed by Felipe Lopes. Change-Id: I5c05b878bde073aeb45bf22340183893f85269e1 --- .../hadoop-aws/src/site/markdown/tools/hadoop-aws/committers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/committers.md b/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/committers.md index ac03bdcdb7..dee77b62e6 100644 --- a/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/committers.md +++ b/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/committers.md @@ -789,7 +789,7 @@ This surfaces when either of two conditions are met. `fail` and the output/destination directory exists. The job will fail in the driver during job setup. 1. The Partitioned Committer is used with `fs.s3a.committer.staging.conflict-mode` set to -`fail` and one of the partitions. The specific task(s) generating conflicting data will fail +`fail` and one of the partitions exist. The specific task(s) generating conflicting data will fail during task commit, which will cause the entire job to fail. If you are trying to write data and want write conflicts to be rejected, this is the correct