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

   ABFS built list-status entry paths with File.separator, which is a backslash 
on Windows. Path("\name:x") then treats "\name" as a URI scheme, so listing a 
directory whose children contain a colon failed with URISyntaxException. Use a 
forward slash unconditionally.
   
   
   ### Description of PR
   This PR to fix the bug: 
[HDFS-17881](https://issues.apache.org/jira/browse/HDFS-17881)
   
   ### How was this patch tested?
   Use test_hadoop_azure.zip on the ticket to test this issue: the details is 
in java file
   AbfsListStatusOAuthTest.java
   
   ### For code changes:
   
   - [x ] Does the title of this PR start with the corresponding JIRA issue id 
(e.g. 'HADOOP-17881. Hadoop file system can not browse the folder that has 
children folder with colon in Windows')?
   - [ ] Object storage: Have the integration tests been executed and the 
endpoint
         declared according to the connector-specific documentation? *Note: 
Automated CI
         testing doesn't cover all cases so manual testing with cloud storage 
is still
         required.*
   - [ ] 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:
   
   - [x ] The PR includes the phrase "Contains content generated by Claude for 
creating Unit test"
         where Claude 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
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to