[
https://issues.apache.org/jira/browse/HADOOP-16153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-16153:
------------------------------------
Resolution: Duplicate
Status: Resolved (was: Patch Available)
1. closing as a duplicate
2. resubmitting HADOOP-16058 as a github PR for easy review
[~uprush] can you take a look at that patch, and if you are testing against
your own s3 endpoints, try running the hadoop-aws test against it to see that
it works. And if you are using the terasort for some benchmarking, share any
numbers you can :)
> Allow TeraGen to use schema-specific output committer
> -----------------------------------------------------
>
> Key: HADOOP-16153
> URL: https://issues.apache.org/jira/browse/HADOOP-16153
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.1.1
> Reporter: Yifeng Jiang
> Assignee: Yifeng Jiang
> Priority: Minor
> Attachments: HADOOP-16153.patch
>
>
> TeraGen is hard-coded to use FileOutputCommitter to commit the job. This
> patch is to allow TeraGen to use schema-specific committer for optimization.
> For example, using S3A committers for s3a:// object storage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
