If the code is wrong: submit a patch with the fix & tests. If you can't get things to work because the docs are wrong: file a JIRA with a patch. For benchmark consistency, leave S3Guard on. If you do that: I'd like to see the numbers comparing FileOutputCommitter (which must have S3Guard) and the new committers. Bit of JSON naming committer, files committed and some metrics ( SuccessData) and you are using an S3 committer. 0-bytes long: classic FileOutputCommitter. switch s3a:// to use that committer: fs. = partitioned.Initially I'd use the staging committer, specificially the 'directory' on. If you want to use the magic committer turn S3Guard on.Tip for the Uber team: git-secrets is something you can add as a checkin hook.
Following up from yesterday's post on the S3A committers, here's what you need for picking up the committers.
