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

Stateful operation is probably not safe, and should be marked as such #252

Open
johnynek opened this issue Dec 17, 2012 · 0 comments
Open
Assignees
Milestone

Comments

@johnynek
Copy link
Collaborator

http://docs.cascading.org/cascading/1.2/javadoc/cascading/operation/BaseOperation.html#isSafe()

By default, cascading (and hence scalding) assumes you can rerun the same map operation over and over (that is, idempotency is assumed). For a stateful operation, you might be talking to a server and doing some non-idempotent operation.

We should either make it clearer in the docs that idempotency is assumed and/or allow the programmer to signal to cascading that it is not (and we set isSafe == false).

I prefer to tell everyone that scalding addresses the idempotent case, and if you want to go beyond, write your own operation and use .each (and you take responsibility). I don't like encouraging non-idempotent operations.

@ghost ghost assigned reconditesea May 23, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants