You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
S3Path.normalize() currently just returns the path unmodified. This is inconvenient for users wanting to use S3FS as a replacement for more unix-like filesystem, where elements '.' and '..' have special meanings ('this directory', and 'parent directory').
We can make S3FS behave more unix-like by having normalize() effectively remove "./" and "<dir>/../".
Notes
S3 itself does not attach special meaning to these filenames, so it is perfectly legal to create an object with key "/abc/../file" distinct from "/file". If we add normalization, we would make such objects inaccessible. If this is particularly unwanted, we could make the behaviour configurable.
Paths.get().normalize() on Windows also treats the .. the same way.
Tasks
The following tasks will need to be carried out:
Implement S3Path.normalize() that normalizes paths as if they were Unix paths.
Task Description
S3Path.normalize() currently just returns the path unmodified. This is inconvenient for users wanting to use S3FS as a replacement for more unix-like filesystem, where elements '.' and '..' have special meanings ('this directory', and 'parent directory').
We can make S3FS behave more unix-like by having normalize() effectively remove "./" and "<dir>/../".
Notes
Paths.get().normalize()
on Windows also treats the..
the same way.Tasks
The following tasks will need to be carried out:
Help
The text was updated successfully, but these errors were encountered: