Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
gsutil work with explicit directories
See original GitHub issuegcsfuse requires explicit directories by default. So the bucket has object:
dir/
dir/a.txt
When do gsutils cp, mv, rsync and I need to copy/move the explicit directory too. Reason: gsutil is faster then gcsfuse and the gcsfuse cannot mv (rename) directories. So when I do gsutil mv gs://bucket/dir gs://bucket/newdir, I got the objects:
dir/
newdir/a.txt
but I would expect
newdir/
newdir/a.txt
Similarly with gsutils cp, rsync - the newdir/ explicit directory is not created.
Note: as a workaround I have created a shell script to create explicit dirs gsmkdirs.sh.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:6
- Comments:20 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1 on something built into gsutil. I can do it from the web console, wonder why doesn’t the cli support?
It’s unlikely we’ll add support for gsutil to create placeholder objects representing directories. gsutil tries to be compatible with these placeholder objects, but it does not create them because it complicates gsutil command semantics.