New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix issue with S3 FS not working with segments with spaces in the name #10055
base: master
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## master #10055 +/- ##
=============================================
+ Coverage 35.06% 70.39% +35.32%
- Complexity 200 5695 +5495
=============================================
Files 1995 1995
Lines 107593 107612 +19
Branches 16353 16359 +6
=============================================
+ Hits 37732 75754 +38022
+ Misses 66611 26555 -40056
- Partials 3250 5303 +2053
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@@ -98,6 +98,8 @@ | |||
*/ | |||
public abstract class SegmentDirectory implements Closeable { | |||
|
|||
public abstract boolean isDirectoryMatchingWithLatestConfigs(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this API stands for?
Can we also add a test to guard the behavior? |
S3PinotFS fails to process segments with spaces in their names. This is due to URI.getPath() returning decoded path while the
.prefix
function expects unescaped path.