On Mon, Sep 10, 2012 at 1:04 AM, Eli Collins wrote:
Peter,
Thanks for the info. Do you guys plan to contribute the rewritten s3
code (assume you're referring to org.apache.hadoop.fs.s3) back to
Apache?
Thanks,
Eli
various failure conditions.
Peter,
Thanks for the info. Do you guys plan to contribute the rewritten s3
code (assume you're referring to org.apache.hadoop.fs.s3) back to
Apache?
Thanks,
Eli
On Sun, Sep 9, 2012 at 12:38 PM, Sirota, Peter wrote:
Hi,
The major differences are in s3 file system that has been rewritten in
EMR and in Hadoop interactions with S3. Other differences are in detectingHi,
The major differences are in s3 file system that has been rewritten in
various failure conditions.
Outside these it's Apache Hadoop. Here is a list of patches EMR applied
on top of 1.0.3 Hadoop
http://docs.amazonwebservices.com/ElasticMapReduce/latest/DeveloperGuide/EnvironmentConfig_AMIHadoopPatches.html
Regards,
Peter
on top of 1.0.3 Hadoop
http://docs.amazonwebservices.com/ElasticMapReduce/latest/DeveloperGuide/EnvironmentConfig_AMIHadoopPatches.html
Regards,
Peter
On Sep 9, 2012, at 11:29 AM, "Momina Khan" wrote:
hi all!
could someone please point out key differences between hadoop code and
Amazon's Elastic MapReduce. I am particularly interested in ways that
hadoop code is changed/optimized to run on efficiently EC2.
cheers!
momina
hi all!
could someone please point out key differences between hadoop code and
Amazon's Elastic MapReduce. I am particularly interested in ways that
hadoop code is changed/optimized to run on efficiently EC2.
cheers!
momina
