Skip to content
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.

AMI 4.x support #125

Merged
merged 5 commits into from Feb 1, 2016
Merged

AMI 4.x support #125

merged 5 commits into from Feb 1, 2016

Conversation

robert2d
Copy link
Collaborator

@robert2d robert2d commented Feb 1, 2016

  • additional info added
  • S3DistCp defaults to new JAR location for AMI >= 4.x

@robert2d robert2d mentioned this pull request Feb 1, 2016
robert2d added a commit that referenced this pull request Feb 1, 2016
@robert2d robert2d merged commit 5423ede into master Feb 1, 2016
@robert2d
Copy link
Collaborator Author

robert2d commented Feb 1, 2016

Hey @fblundun, I made a couple of changes to your code and added a few specs for the new features. but your commits are still in there ;)

@robert2d robert2d deleted the ami-4.x-support branch February 1, 2016 00:30
@fblundun
Copy link
Contributor

Thanks for the release @robert2d , it's working well!

One more question: for AMI 3.x, we had to do some additional Hadoop configuration for a particular input format. This is how we did it using Elasticity's HadoopBootstrapAction.

But in 4.x, predefined bootstrap actions are replaced by configurations. It looks like we should start using the new Elasticity::Application class. Do you have any idea how to translate our old bootstrap logic into an Application configuration?

Many thanks!

@fblundun
Copy link
Contributor

Update: I didn't see a way to set configurations in the Elasticity API so I ended up putting them directly into the payload by monkey patching the AwsRequestV4 class here.

@robert2d
Copy link
Collaborator Author

Yea looks like a new "feature" that needs to added. I'll create an issue for now

@robert2d
Copy link
Collaborator Author

On the subject of Applications you can see them in the readme now here

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants