[
https://issues.apache.org/jira/browse/HADOOP-19917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18087978#comment-18087978
]
ASF GitHub Bot commented on HADOOP-19917:
-----------------------------------------
K0K0V0K opened a new pull request, #8544:
URL: https://github.com/apache/hadoop/pull/8544
### Description of PR
Currently in the org.apache.hadoop.fs.azurebfs.services.AbfsClient if the
sasTokenProvider throws an exception, than the root cause wont be visible in
the logs.
The SasTokenProvider can be a third party entity (for example Ranger
implementation) so debugging can be challenging in these situation.
### How was this patch tested?
CI will run the UTs, no other test happened.
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
### AI Tooling
If an AI tool was used:
- [ ] The PR includes the phrase "Contains content generated by <tool>"
where <tool> is the name of the AI tool used.
- [ ] My use of AI contributions follows the ASF legal policy
https://www.apache.org/legal/generative-tooling.html
> Add cause to exception in AbfsClient if SASTokenProvider failed
> ---------------------------------------------------------------
>
> Key: HADOOP-19917
> URL: https://issues.apache.org/jira/browse/HADOOP-19917
> Project: Hadoop Common
> Issue Type: Improvement
> Components: hadoop-tools
> Affects Versions: 3.5.0
> Reporter: Bence Kosztolnik
> Assignee: Bence Kosztolnik
> Priority: Major
>
> Currently in the *org.apache.hadoop.fs.azurebfs.services.AbfsClient* if the
> sasTokenProvider throws an exception, than the root cause wont be visible in
> the logs.
> The SasTokenProvider can be a third party entity (for example Ranger
> implementation) so debugging can be challenging in these situation.
> Example log snippet
> {code:java}
> Failed to acquire a SAS token for get-status on [[PATH]] due to
> org.apache.hadoop.security.AccessControlException:
> org.apache.ranger.raz.intg.RangerRazException: null response {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
