-
Notifications
You must be signed in to change notification settings - Fork 141
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
Update to exception processing doc #614
Conversation
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
the transform should either | ||
* throw any exception in `__init__()`, or | ||
* throw an UnrecoverableException from AbstractBinaryTransform's `transform_binary`, `flush_binary(), or |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
throwing any exception in __init__()
will not terminate the process. It will just continue re creating an actor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so what happens, effectively, to the actor and the processing of data when init() throws an exception. I would presume that no data is processed by an actor that gets an exception in init(),and since all actors likely get the same exception, all data processing is ended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added more precise doc in #616
Signed-off-by: David Wood <dawood@us.ibm.com>
This was done in PR #616 |
commited additional .md changes, so re-opening |
Why are these changes needed?
clarity
Related issue number (if any).