Larborator opened a new issue, #20072:
URL: https://github.com/apache/doris/issues/20072

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Version
   
   1.2.4.1-rc01
   2.0.0-alpha1
   
   ### What's Wrong?
   
   When using Windows OS as the FE server, error: "UNC path is missing 
sharename: //frontends" is reported when querying the System Info module. 
   
   Details are shown in the following figure: 
   
![bug](https://github.com/apache/doris/assets/19779893/06e330c4-fd26-420c-aa06-92363cc4abfe)
   
   The reason is the results of the method "Paths.get()" running on Windows and 
Linux are different.
   In Linux, '//frontends' will be escaped as '/' but in Window must use 
'/frontends'.
   
   And when a path is "/cluster_health/tablet_health/6005700", in Windows  
method "Path.getParent()" will output as ''\cluster_health\tablet_health" which 
will cause wrong result when using "Parent Dir" button.
   
   
   
   ### What You Expected?
   
   Can get System Info when using Windows OS.
   
   
   
   ### How to Reproduce?
   
   Run fe server in Windows OS.
   
   ### Anything Else?
   
   My solution:
   1. replace request URI 'System?path=//frontends' as 'System?path=/frontends'
   2. when FileSystemSeparator is WindowsFileSystemSeparator( '\'), replace '\' 
as '/'
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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