-
Notifications
You must be signed in to change notification settings - Fork 996
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
Unserializable FluentBackoff cause null pointer exception in Dataflow Runner #417
Unserializable FluentBackoff cause null pointer exception in Dataflow Runner #417
Conversation
@@ -11,7 +11,7 @@ | |||
|
|||
public class BackOffExecutor implements Serializable { | |||
|
|||
private static FluentBackoff backoff; | |||
private FluentBackoff backoff; |
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.
Maybe it was meant to be final
instead? Seems like it can be.
c593859
to
48dd24d
Compare
48dd24d
to
5778ad0
Compare
/lgtm |
/retest |
1 similar comment
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: khorshuheng, zhilingc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Backoff variable has been mistakenly assigned the static modifier. This doesn't affect DirectRunner, but on Dataflow Runner this seems to result in Nullpointer exception.
Edited: FluentBackoff shouldn't have been setup on the constructor, as it is unserializable. Passing the backoff as function argument fixed this. Thanks to @zhilingc for helping me to identify this.