Closed kpfaulkner closed 8 years ago
Reported that copying (fake) subdirectories from S3 to Azure was messing up the target blob name. Specifically if S3 has:
..../dir1/dir2/file1 and ..../dir1/dir2/file2
On Azure the final blob names would be:
..../dir2\file1 and ..../dir2\file2
Need to investigate this to see renaming was intentional (for some use case) or if simply a bug.
fixed in 1.1.2
Reported that copying (fake) subdirectories from S3 to Azure was messing up the target blob name. Specifically if S3 has:
..../dir1/dir2/file1 and ..../dir1/dir2/file2
On Azure the final blob names would be:
..../dir2\file1 and ..../dir2\file2
Need to investigate this to see renaming was intentional (for some use case) or if simply a bug.