-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Bug]: Python GCSFileSystem.delete does not recursively delete #27605
Comments
Thanks for reporting! What happens if you delete |
https://stackoverflow.com/questions/52789714/google-cloud-storage-how-to-delete-a-folder-recursively-in-python has some examples how to fetch objects starting with a particular prefix. might be easier once #25676 is fixed. |
cc: @BjornPrime |
.take-issue |
Yup, I'm aware :) That does remove all the objects, but doesn't "recursively" work. FYI the |
@ AnandInguva Is this issue update ? |
cc @shunping |
Can I pick it ? |
@tsafacjo Please do that. Some guides are here: https://github.com/apache/beam/blob/master/contributor-docs/code-change-guide.md and https://beam.apache.org/contribute/#ways-you-can-contribute. Thanks! |
thanks |
@liferoad it looks like if this PR https://github.com/apache/beam/pull/29477/files#diff-c12c6d027caa8ddf49ae5488f38ebbdf798e8ae85d7d0d716c0ebd8cce9477fe already solved the problem. |
@AnandInguva what is the problem for your PR? |
What happened?
In the Python SDK,
GCSFileSystem.delete
suggests directories will be deleted recursively, but that doesn't appear to be the case...?e.g.I have bucket
blakely_dev
and the following paths:gs://blakely_dev/_staging/iteration/1/result
gs://blakely_dev/_staging/iteration/1/output-00000-of-00002
gs://blakely_dev/_staging/iteration/1/output-00001-of-00002
If I pass
gs://blakely_dev/_staging/
to.delete()
, despite it being a directory and a wildcard being appended if it ends with a/
, the following.match()
call within.delete()
matches neither subdirectories nor theresult
oroutput-0000.*
files.Issue Priority
Priority: 3 (minor)
Issue Components
The text was updated successfully, but these errors were encountered: