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

CommonCrawlFetcher should limit bytes requested to max content size #77

Open
kkrugler opened this issue Nov 10, 2017 · 0 comments
Open
Labels

Comments

@kkrugler
Copy link
Member

Currently if there's a constraint on the max data to read, and it's less than the size of the page, we get:

2017-11-10 13:24:53,796 WARN  internal.S3AbortableInputStream      - Not all bytes were read from the S3ObjectInputStream, aborting HTTP connection. This is likely an error and may result in sub-optimal behavior. Request only the bytes you need via a ranged GET or drain the input stream after use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant