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

Calculation and Turing-Completeness #48

Open
GoogleCodeExporter opened this issue Mar 28, 2015 · 10 comments
Open

Calculation and Turing-Completeness #48

GoogleCodeExporter opened this issue Mar 28, 2015 · 10 comments

Comments

@GoogleCodeExporter
Copy link

FIrst off- it's nice. I come from the Unix tradition of short&sweet. Of course, 
I want a new feature :)

Hadoop workflow drivers all seem to believe in code&fire&forget: some allow 
if/then/else branching and oozie supports expressions. I have not found any 
that support conditionally starting over or jumping into the middle.

Many machine learning algorithms use repetitive calculations driving towards a 
finishing condition (often a maximum error value). The Mahout project, which 
focuses on machine learning on Map/Reduce, has a great many multistage 
calculation jobs which have to be coded in Java entirely due to this.

Here is a very simple feature addition that would solve all of these: a 
decision node that calls a Java object. One of the possible decisions would be: 
branch X is a goto to another place in the workflow. This would hack the 
generation numbers on the paths after the target node.


Original issue reported on code.google.com by lance.no...@gmail.com on 31 Jul 2011 at 11:27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant