-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
aws s3 sync re-uploads files that are already in target location #843
Comments
I have the same problem and I added some extra debug info in Comparator class to see what's going on.
For the first some files the keys would be completely different, e.g.:
Notice that the destination compare_key is equal in all cases. Then after it actually reaches this file, it straightens out and starts comparing correctly:
But later it would get out of sync again and repeat the pattern. Let me know if you need more info. |
Thank you @kyleknap! Very appreciated. |
Fixed by pull request: #865 |
Thanks |
* Introduce StreamWriter to wrap output streams. Fix aws#835 * Fix typo
Using 1.3.21 of aws cli on Windows 7
Appears that having a folder name which starts with another folder name at the same level causes aws cli to believe that the files in that directory do not exist, and therefore re-uploads them. This conclusion based on running the following (with and without comparator):
aws s3 sync "C:\abc" "s3://my_bucket_name/abc"
c:\abc contains some files and 2 folders "xyz" and "xyz2". The first time it runs successfully and I have verified that everything has been copied to the s3 bucket. On every subsequent run all the files in c:\abc\xyz are re-uploaded erroneously.
I was puzzling as to what was going on (including investigation of #599). There is a thread about this in the aws forum https://forums.aws.amazon.com/thread.jspa?threadID=146851&tstart=0
The text was updated successfully, but these errors were encountered: