-
Notifications
You must be signed in to change notification settings - Fork 6
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
Switch gcp.copy to use rewrite calls #349
Comments
ttung
pushed a commit
that referenced
this issue
Jan 12, 2018
Unlike S3 copy, GS copy cannot be parallelized. However, it has a token that can be used to continue a rewrite call. Connects to #349
ttung
pushed a commit
that referenced
this issue
Jan 12, 2018
Unlike S3 copy, GS copy cannot be parallelized. However, it has a token that can be used to continue a rewrite call. Connects to #349
ghost
added
the
in progress
label
Jan 12, 2018
ttung
pushed a commit
that referenced
this issue
Jan 12, 2018
Unlike S3 copy, GS copy cannot be parallelized. However, it has a token that can be used to continue a rewrite call. Connects to #349
ttung
pushed a commit
that referenced
this issue
Jan 18, 2018
Unlike S3 copy, GS copy cannot be parallelized. However, it has a token that can be used to continue a rewrite call. Connects to #349
ttung
pushed a commit
that referenced
this issue
Jan 18, 2018
Unlike S3 copy, GS copy cannot be parallelized. However, it has a token that can be used to continue a rewrite call. Connects to #349
ttung
added a commit
that referenced
this issue
Jan 18, 2018
Unlike S3 copy, GS copy cannot be parallelized. However, it has a token that can be used to continue a rewrite call. Connects to #349
What is the status on this? |
This is done. |
ghost
removed
the
in progress
label
Feb 5, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: