You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have a use case where I am using s5cmd as a "stash" for user's uncommitted files from Perforce and this has been working great in terms of speed, however Perforce takes the timestamps on the files in account when determining if the user need to refresh their working space.
I am looking to see if we can include a flag that will record timestamps of files in the s3 metadata and then re-apply them during download. I'll see if I can get a PR up to help with this.
Thanks!
-Alex
The text was updated successfully, but these errors were encountered:
this is also critical for the sync command that was introduced in 2.0.0. aws s3 syncdoes preserve the timestamps of the files, so if you sync a directory from S3 to local and then turn right back around and sync it back to S3, it's a no-op because the sizes and timestamps haven't changed. if you try to do that with s5cmd, it copies every single file back up to S3, because it changes the last modified timestamps when it syncs the directory down from S3.
(the actual use case here involves changing/adding some files between the download and the upload.)
Yes, I also agree that s5cmd should preserve timestamp as it would be in case of aws s3. I got into below issue today trying to figure out why my files look older than expected:
Hi, I have a use case where I am using s5cmd as a "stash" for user's uncommitted files from Perforce and this has been working great in terms of speed, however Perforce takes the timestamps on the files in account when determining if the user need to refresh their working space.
I am looking to see if we can include a flag that will record timestamps of files in the s3 metadata and then re-apply them during download. I'll see if I can get a PR up to help with this.
Thanks!
-Alex
The text was updated successfully, but these errors were encountered: