[ 
https://issues.apache.org/jira/browse/HADOOP-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18085922#comment-18085922
 ] 

ASF GitHub Bot commented on HADOOP-19909:
-----------------------------------------

steveloughran opened a new pull request, #8531:
URL: https://github.com/apache/hadoop/pull/8531

   Explain why a key is invalid and print the relevant option name/account
   
   
   ### How was this patch tested?
   
   * Some manual experiments through storediag
   * rerun of abfs.
   
   ### 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




> Improve abfs diagnostics on auth setup falures
> ----------------------------------------------
>
>                 Key: HADOOP-19909
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19909
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/azure
>    Affects Versions: 3.4.3
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>
> When abfs is misconfigured for auth it's pretty hard to work out what the 
> failure is as there are too many options.
> Print some hints about where the error is so people don't have to immediately 
> reach for storediag. In particular: the account name of relevance



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to