Closed levin81 closed 7 years ago
I guess there is no easy way to fix this. From this page,
A note about directories. S3 of course has no "native" support for them. The idiom we choose then is: for any directory created by this class, we use an empty object "#{dirpath}_$folder$" as a marker. Further, to interoperate with other S3 tools, we also accept the following: - an object "#{dirpath}/' denoting a directory marker - if there exists any objects with the prefix "#{dirpath}/", then the directory is said to exist - if both a file with the name of a directory and a marker for that directory exists, then the file masks the directory, and the directory is never returned.
So the fact that there only appears to be a "+tmp_$folder$" file and no folder by itself is fine?
How did you check that there was no +tmp folder, there must be one actually.
I looked in the S3 directory. In the beginning there was only the "+tmp_$folder$" file but after a while (few hours) the directory was created. Nevermind :-)
This does not seem like an issue, closing it. Reopen if you see it.
When using s3n protocol, many "folder" files (sized 0 bytes) are generated along their respective folders with $ in their names, like "all_$folder$".
Some of the folders themselves aren't even created and only these dollar named files are, like "+tmp_$folder$". Even though this is printed in the logs:
No +tmp directory created :-\ Only the 0 byte file.
Is there an elegant way of stopping the generation of these files? In s3a this doesn't occur but using that seems buggy at the moment (I need to open another issue for this) so I've resorted to s3n.
Thanks