-
Notifications
You must be signed in to change notification settings - Fork 55
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
opendir() fails on same path that listdir() works on #80
Comments
I think this is probably related to https://fs-s3fs.readthedocs.io/en/latest/#limitations , and to previosly reported issues such as #62 and others. It can be tricky to use S3FS on buckets where files were previously created e.g. with boto3, because the presence e.g. of file “foo/bar” does not imply the existence of a directory object "foo/" (which is an empty object with key "foo/") . S3FS instead requires the presence of such objects for some operations. if you try with s3.makedir("/path/to/directory") than listdir should work. As an alternative you could look at #60 and at https://github.com/mrk-its/s3fs |
So I get the S3 empty object thing but I've been doing some thinking and I think, with some finagling, it may be possible to simulate nonexistent directories by using prefix-based searching instead of relying on empty objects as "sentinels" for lack of a better term. This would complicate somethings like |
Not sure why, but
opendir()
apparently only works on the root directory. If you try to use it with a subdirectory that exists, you get a ResourceNotFound error.I've tried this both with the leading and trailing slash and it still breaks.
If I try this...
So far so good. However, if I try using
filterdir()
it breaks even though I was just able to open a.txt
file:I suspect something's wrong with the way SubFS is getting created.
(Duplicate of #8 but that was closed a long time ago with no resolution)
The text was updated successfully, but these errors were encountered: