Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clusters, not job flows #1082

Closed
coyotemarin opened this issue Jul 14, 2015 · 2 comments · Fixed by #1226
Closed

clusters, not job flows #1082

coyotemarin opened this issue Jul 14, 2015 · 2 comments · Fixed by #1226
Labels
Milestone

Comments

@coyotemarin
Copy link
Collaborator

Issue #876 replaces references to "job flows" with "clusters" internally, but leaves exposed methods, logging messages, etc. as-is.

We should use "cluster" wherever we currently use "job flow". The old names should still work until v0.6.0.

@coyotemarin coyotemarin added this to the v0.5.0 milestone Jul 14, 2015
alejandro-rivera added a commit to alejandro-rivera/mrjob that referenced this issue Jul 15, 2015
@coyotemarin coyotemarin modified the milestones: v0.5.0: Code Complete, v0.5.0: Final Cleanup Nov 25, 2015
@coyotemarin coyotemarin modified the milestones: v0.5.0: Final Cleanup, v0.5.0 Jan 15, 2016
@coyotemarin
Copy link
Collaborator Author

Places where we still need to use "job flow" in the code:

  • boto's add_jobflow_steps(), run_jobflow() and terminate_jobflow() (the API calls haven't even been renamed)
  • JobFlowRole param to RunJobFlow

@coyotemarin
Copy link
Collaborator Author

Ack, even the JOB_FLOW runner cleanup option needs to be renamed.

coyotemarin pushed a commit that referenced this issue Feb 21, 2016
Use "cluster" in place of "job flow". Fixes #1082.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant