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

Add support for reserializing CRAM containers #1606

Open
cmnbroad opened this issue Apr 20, 2022 · 0 comments · May be fixed by #1609
Open

Add support for reserializing CRAM containers #1606

cmnbroad opened this issue Apr 20, 2022 · 0 comments · May be fixed by #1609
Assignees
Labels

Comments

@cmnbroad
Copy link
Collaborator

cmnbroad commented Apr 20, 2022

There are cases where we want to be able to re-serialize CRAM containers into a new stream without fully decoding and then re-encoding them (and without the need for the reference). For example, if we want to stitch together CRAM shards that were created in parallel (i.e, as Disq does), or if want to split a CRAM up into smaller CRAMs while preserving existing container boundaries. The main thing required is a means to update the stream-relative values that are in the container and slice headers, specifically the global record counter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant