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

Fix Dataflow translator bug #643

Merged
merged 1 commit into from
Apr 27, 2020

Conversation

zhilingc
Copy link
Collaborator

What this PR does / why we need it:

Fixes bug as described in #642 . If no metrics output is configured, WriteFailureMetricsTransform is a transform with no nodes, which is probably why it throws the error. Added a noop DoFn. Tested this fix locally (with dataflow) and it works.

Which issue(s) this PR fixes:

Fixes #642

Does this PR introduce a user-facing change?:

NONE

@feast-ci-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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

@mrzzy
Copy link
Collaborator

mrzzy commented Apr 23, 2020

This seems to have fixed the issue. Dataflow Jobs are created normally with this fix.
Should we wait for End to End Dataflow tests (#595) or should we just merge this as is?

@khorshuheng
Copy link
Collaborator

/lgtm

@feast-ci-bot feast-ci-bot merged commit 45e6500 into feast-dev:master Apr 27, 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.

Feast Core: Dataflow Runner fails to start job with no translator registered error.
4 participants