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

Unserializable FluentBackoff cause null pointer exception in Dataflow Runner #417

Merged
merged 1 commit into from
Jan 8, 2020

Conversation

khorshuheng
Copy link
Collaborator

@khorshuheng khorshuheng commented Jan 8, 2020

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.

@@ -11,7 +11,7 @@

public class BackOffExecutor implements Serializable {

private static FluentBackoff backoff;
private FluentBackoff backoff;
Copy link
Member

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.

@khorshuheng khorshuheng force-pushed the bugfix-static-backoff branch 2 times, most recently from c593859 to 48dd24d Compare January 8, 2020 06:28
@khorshuheng khorshuheng changed the title Private static variable cause null pointer exception in Dataflow Runner Unserializable FluentBackoff cause null pointer exception in Dataflow Runner Jan 8, 2020
@zhilingc
Copy link
Collaborator

zhilingc commented Jan 8, 2020

/lgtm

@zhilingc
Copy link
Collaborator

zhilingc commented Jan 8, 2020

/retest

1 similar comment
@zhilingc
Copy link
Collaborator

zhilingc commented Jan 8, 2020

/retest

@zhilingc
Copy link
Collaborator

zhilingc commented Jan 8, 2020

/approve

@feast-ci-bot
Copy link
Collaborator

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@feast-ci-bot feast-ci-bot merged commit c82ba8f into feast-dev:master Jan 8, 2020
khorshuheng added a commit to khorshuheng/feast that referenced this pull request Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants