skyyyy955 opened a new pull request, #10910:
URL: https://github.com/apache/paimon/pull/10910

   ### Purpose
   
   `testReadFileUriWithUnescapedCharacters` prepends `file://` to a native 
path. On Windows, the drive letter and backslashes are parsed as an authority, 
so the test fails before reading the file.
   
   Construct the test input from `file.toUri()` through Paimon's 
`Path.toString()`. This preserves the unescaped Unicode filename and space 
while using the platform's URI path structure. The change is limited to one 
test line; the reader implementation and assertions are unchanged.
   
   This adjusts the test fixture introduced by LsomeYeah in #8931 
(`4adce1d41bc56d795077f446baa9e0f1ca41f8b0`).
   
   ### Tests
   
   On 1902379e544e233b9ca9ec4d452db796a53c3f0e, ran the full 
`UriReaderFactoryTest` with JDK 8:
   
   | Platform | Before | After |
   | --- | --- | --- |
   | Windows | 14 passed, 1 error in the unescaped-path test | 15 passed |
   | Linux | 15 passed | 15 passed |
   
   `mvn -o -B -ntp -pl paimon-common -am -DwildcardSuites=none 
-DfailIfNoTests=false -Dtest=UriReaderFactoryTest test`
   
   No fast-build profile. Spotless and Enforcer passed; Checkstyle passed on 
Linux. The Windows checkout is under a target directory and falls under the 
existing Checkstyle suppression. `git diff --check` passed. Full-module tests 
and RAT were not run.
   
   The branch is based on `0369648333b9278d4d61a0768cf355f3299ec111`. All 
inputs in the selected parent/API/test-utils/common reactor, all POM files and 
the Java test/build configuration are identical to the tested base; the 31 
differing files are Python code/CI, video-format production code and tests, a 
core test, and documentation outside this test scope. The one-line patch is 
unchanged. Tests were not repeated after rebasing.
   


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

Reply via email to