-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add in selective pushing/pulling from s3 #23
Comments
@larryfenn The push/pull commands delegate to the AWS cli sync command, which should only send new or updated files to the target destination. When you run Can you run a test in your shell that demonstrates a case where files that have not been changed are actually being synced and paste the shell session contents here? |
@larryfenn One additional thought -- I wonder if the time delay you mentioned is not in fact due to sending of unchanged files, but in performing a diff operation to determine what has actually changed between the source and destination (akin to the long wait you might experience when using |
@larryfenn Sorry, one final thought as a stop-gap workflow. The But the AWS sync command also has |
Right now, datakit data pushes and pulls the entire contents of the data directory, even for files that haven't changed. This causes pushes and pulls to take much more time than they should in some projects.
Instead, datakit data should only push and pull files that have changed between disk and s3. Is there a s3 flag that we can pass through (and then make the default)?
The text was updated successfully, but these errors were encountered: