Fix Hadoop S3 Key settings#1007
Merged
Merged
Conversation
xiaoyongzhu
approved these changes
Jan 20, 2023
jainr
approved these changes
Jan 21, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Resolves #XXX
How was this PR tested?
Currently, if S3 keys are not provided, they are automatically set as "None" in the hadoop configurations. This prevents S3 IAM role from being used instead of the keys. This change ensures that the Hadoop configuration for the S3 keys is only set when the keys are provided. Otherwise, ignored.
@xiaoyongzhu this PR is regarding the change we discussed
Does this PR introduce any user-facing changes?