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 BigQuerySink successful output to produce only once #858

Merged
merged 1 commit into from
Jul 3, 2020

Conversation

pyalex
Copy link
Collaborator

@pyalex pyalex commented Jul 2, 2020

What this PR does / why we need it:

Make sure successful inserts are not duplicated in BigQuerySink. When we joining rows-to-be-inserted with bq-write output it should emit only once.

In addition I made BigQuerySinkTest more stable since it was failing periodically.

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:


@pyalex pyalex force-pushed the fix-bq-success-out branch from cc46bf4 to 810b834 Compare July 3, 2020 09:19
@pyalex
Copy link
Collaborator Author

pyalex commented Jul 3, 2020

/test test-end-to-end-auth

@pyalex
Copy link
Collaborator Author

pyalex commented Jul 3, 2020

/test test-end-to-end-batch

@feast-ci-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pyalex, woop

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

@woop
Copy link
Member

woop commented Jul 3, 2020

/lgtm

@feast-ci-bot feast-ci-bot merged commit 2e7a00a into feast-dev:master Jul 3, 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.

3 participants