Skip to content

Bump hadoop aws version to 3.2.0 for local launcher #64

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.

Sign up for GitHub

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

Jump to bottom
Open
unit7-0 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Bump hadoop aws version to 3.2.0 for local launcher #64

unit7-0 wants to merge 1 commit into from

Conversation

@unit7-0
Copy link

@unit7-0 unit7-0 commented Apr 27, 2021

Signed-off-by: breezzo vialurt@gmail.com

What this PR does / why we need it:
Bump hadoop aws version to 3.2.0 since the fs.s3a.path.style.access option is not available in 2.7.3 which makes it difficult to run spark jobs locally with minio.
I looked the version numbers in the Dockerfile https://github.com/feast-dev/feast-spark/blob/master/infra/docker/spark/Dockerfile
Maybe there any reasons why versions shouldn't be updated?

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

NONE

@unit7-0
Up hadoop aws to fix s3 path style problem in local mode
b15deb8 
Signed-off-by: breezzo <vialurt@gmail.com>
@feast-ci-bot
Copy link
Collaborator

feast-ci-bot commented Apr 27, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: unit7-0
To complete the pull request process, please assign pyalex after the PR has been reviewed.
You can assign the PR to them by writing /assign @pyalex in a comment when ready.

The full list of commands accepted by this bot can be found 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

@feast-ci-bot
Copy link
Collaborator

feast-ci-bot commented Apr 27, 2021

Hi @unit7-0. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

needs-kind needs-ok-to-test release-note-none size/XS

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@unit7-0 @feast-ci-bot