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

jets3t -> aws sdk #1394

Merged
merged 2 commits into from
Jan 9, 2017
Merged

jets3t -> aws sdk #1394

merged 2 commits into from
Jan 9, 2017

Conversation

ssalinas
Copy link
Member

@ssalinas ssalinas commented Jan 9, 2017

Moving us to the aws sdk. This is partly just to keep up to date, but also so that we can use the new GetObjectV2 to do pagination when listing buckets in the future.

aws.sdk.version is bumped to 1.10.77 for now. 1.10.x is the first to have the new v2 request (basepom has 1.9.x). Going all the way to 1.11.x created too many dependency issues.

PRing this into the other S3 rework branch.

/cc @tpetr

@@ -131,7 +131,7 @@ public void setLocalDownloadPath(String localDownloadPath) {
this.localDownloadPath = localDownloadPath;
}

public long getS3ChunkDownloadTimeoutMillis() {
public Long getS3ChunkDownloadTimeoutMillis() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why Long here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in order to more cleanly call intValue() (aws sdk takes an int). Was debating if it was cleaner to keep the TimeUnit.SECONDS.toMillis(30)so the default is readable and have to do long -> int, or to move it all to int. Reading it now the second probably makes more sense, I'll update

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say let's change this to int. The max value of a Java integer in milliseconds is a little more than 24 days, which should be more then enough for this timeout.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

@tpetr
Copy link
Contributor

tpetr commented Jan 9, 2017

LGTM

@ssalinas
Copy link
Member Author

ssalinas commented Jan 9, 2017

This is working fine in staging, going to merge it with the other s3-related PR

@ssalinas ssalinas merged commit 9db459b into s3_rework Jan 9, 2017
@ssalinas ssalinas deleted the jets_to_aws branch January 9, 2017 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants