Skip to content

Use existing staging client for dataproc staging - #1063

Merged
feast-ci-bot merged 1 commit into
feast-dev:masterfrom
khorshuheng:refactor-staging-client
Oct 16, 2020
Merged

Use existing staging client for dataproc staging#1063
feast-ci-bot merged 1 commit into
feast-dev:masterfrom
khorshuheng:refactor-staging-client

Conversation

@khorshuheng

Copy link
Copy Markdown
Collaborator

Signed-off-by: Khor Shu Heng khor.heng@gojek.com

What this PR does / why we need it:
Currently, the dataproc launcher is using it's own implementation of staging client rather than reusing existing staging client in feast.staging.storage_client. This PR consolidate the implementation.

This would also help #1061 to use the existing staging client as well.

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

NONE

…client for s3

Signed-off-by: Khor Shu Heng <khor.heng@gojek.com>
@feast-ci-bot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@pyalex

pyalex commented Oct 16, 2020

Copy link
Copy Markdown
Collaborator

/lgtm

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