only check for delegation token from NN when it is non S3 filesystem #50
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 of PR
We have an issue where writing to S3 fails because we're checking delegation token before writing in FileOutputFormat. Normally call to
TokenCache.obtainTokensForNamenodes
shouldn't fail in this case of writing to S3 because it returns if security isn't enabled, but we have jobs that can do lots of things and within it also makes calls to HBase to authenticate and thus creates problem for FileOutputFormat writing to S3.How was this patch tested?
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?