Skip to content
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 used in conjunction with filters somtimes re-downloads unmodified file #794

Closed
rahul-amaram-vizury opened this issue May 29, 2014 · 2 comments · Fixed by #993
Assignees
Labels
bug This issue is a bug. s3sync s3

Comments

@rahul-amaram-vizury
Copy link

aws s3 sync s3://test-bucket/rahul-dev/archive/ /tmp/archive/ --exclude '*' --include rahul-dev/archive/Application.jar --debug 2>&1 | grep comparator

So, what I am trying to do is to sync s3://test-bucket/rahul-dev/archive/Application.jar to destination folder only if it has changed. But everytime I run this, it re-downloads with the debug statement file does not exist in destination. Is there any fix for this? Is there a better way for identifying changed files from s3 and then only downloading them?

@jamesls
Copy link
Member

jamesls commented Jun 4, 2014

This appears to be a bug when using sync with only a portion of the bucket, i.e instead of s3://bucket/ /local you use s3://bucket/path/to/thing /local/path/to/thing. Investigating a fix.

@bounav
Copy link

bounav commented Aug 22, 2014

Another example of that bug (or a very similar one) is the following command. It re-downloads everything matching the filters (in other words it doesn't sync but copies):

aws s3 sync s3://bucket /path/to/local/folder --exclude "*.ext" --include "b*"

The intent of the command above is to sync all b*.ext files from the bucket to a local folder.

I tried with --size-only and it copies everything over regardless of whether some files have already been downloaded or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. s3sync s3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants