-
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
Add support to Python SDK for staging files on Amazon S3 #769
Conversation
Hi @jmelinav. Thanks for your PR. I'm waiting for a feast-dev member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
bb59e57
to
f1cc709
Compare
eded390
to
c1e1d91
Compare
/ok-to-test |
/test test-end-to-end |
/assign @pyalex |
Can you please also add a note in the release log that you have added |
Sounds good to me, I have removed the fixes #706 from the PR description and mentioned it addresses only python client changes. Also I have appended to |
a8d433e
to
9ae9665
Compare
/test test-end-to-end-batch |
9ae9665
to
8823058
Compare
/test test-end-to-end |
/test test-end-to-end-auth |
/test test-end-to-end-batch |
/test test-end-to-end |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jmelinav, 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 |
/lgtm |
What this PR does / why we need it:
Currently Feast client cannot stage data anywhere except GCP storage. The PR adds S3 staging support on client.
Which issue(s) this PR fixes: Client can stage files on s3.
Python Client changes for #706.
Edit: Fixes #562
Does this PR introduce a user-facing change?: No