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

Address full object request corner case and resolve file format extension #104

Closed
wants to merge 7 commits into from

Conversation

brainstorm
Copy link
Member

@brainstorm brainstorm commented Jun 29, 2022

Thanks @victorskl for reporting this issue, it exposes a few areas that need improvement, namely this excessive fetching in the AWS backend.

How to reproduce

export HTSGET_STORAGE_TYPE=AwsS3Storage
export HTSGET_S3_BUCKET=umccr-research-dev
cargo run -p htsget-http-actix &
curl -s 'http://127.0.0.1:8080/reads/example.bam'  <--- See Slack's UMCCR #htsget-rs for a more suitable one

I will address the failing tests next, but with these changes @victorskl would be able to get htsget-rs to not block on big files (114G) on the reproducer we discussed.

higher abstraction level so that potentially all
storage backends can benefit from it.

Co-authored-by: @mmalenic
…ole file bigger than 4294967295 bytes, we'd have a problem. This still doesn't fix the egressing of bytes when the response should be a few bytes JSON with the whole start-end byterange of a big S3 object [ci skip]
@brainstorm brainstorm changed the title Address full object request corner case and resolve file format extension fix Address full object request corner case and resolve file format extension Jun 29, 2022
@brainstorm
Copy link
Member Author

@mmalenic I suspect that PR #107 already solves this? Otherwise could you add those changes where appropriate there or close this?

@mmalenic mmalenic closed this Aug 4, 2022
@mmalenic
Copy link
Member

mmalenic commented Aug 4, 2022

Closed, as this is addressed in #107.

@mmalenic mmalenic deleted the resolve_extension_fix branch August 4, 2022 03:12
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