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

Allow retrying on failure for HTTPRangedByteAccess #343

Merged
merged 1 commit into from
Aug 20, 2014

Conversation

carlyeks
Copy link
Member

The pushes the retry logic down into HTTPRangedByteAccess instead of in the tests; this allows us to also use this in the ParquetRDD class.

@@ -19,24 +19,41 @@ package org.bdgenomics.adam.io

import java.io.InputStream
import java.net.URI
import org.apache.http.{ HttpResponse, Header }
import org.apache.http.client.HttpClient
import org.apache.http.client.methods.{ HttpGet, HttpHead }
import org.apache.http.impl.client.DefaultHttpClient
import org.apache.spark.Logging

Copy link
Member

Choose a reason for hiding this comment

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

Nit: extra space.

@fnothaft
Copy link
Member

@carlyeks can you rebase this?

@carlyeks
Copy link
Member Author

Sad face...Probably need to try something else...

@fnothaft
Copy link
Member

Move the test files to S3? Let's not close this though, it's still a useful contribution.

@massie
Copy link
Member

massie commented Aug 7, 2014

Jenkins, test this please.

@fnothaft
Copy link
Member

@carlyeks pinging here, can you rebase this and push the change with the berkeley/s3 URLs swapped then let's get this merged.

@fnothaft
Copy link
Member

@carlyeks pinging here again... any updates/an ETA?

@tdanford
Copy link
Contributor

Ping @carlyeks

fnothaft added a commit that referenced this pull request Aug 20, 2014
Allow retrying on failure for HTTPRangedByteAccess
@fnothaft fnothaft merged commit 7573b0e into bigdatagenomics:master Aug 20, 2014
@fnothaft
Copy link
Member

Merged! Thanks @carlyeks!

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.

4 participants