Open brianlenz opened 7 months ago
Hi @brianlenz, I encountered the same issue and although your relocation approach works, I noticed that my issue was to not have a trailing slash in the sourcePath. Thus, sync selected paths like s3://bucket-a/x/y/zabc
and mixed up the relocation.
However, I agree that there seems to be an issue with the relocation when the sourcePath is ending with a fraction of a directory name of a file in the source bucket.
It looks like paths get duplicated unexpectedly when doing an S3 -> S3 sync. In this use case, the sync only includes files in sub-folders of the bucket. For some reason, the path that the files are located in are duplicated unexpectedly in the destination key.
It's easiest to represent through code:
In this example, in transferring from
x/y/z
tox/y/z
, the destination folder is actuallyx/y/z//x/y/z
(note the double//
in the middle of the path, too).For now, we've worked around it using
relocations
as shown above, but it seems like this is probably a bug that should be fixed?