Use XZ for LZMA compression in CRAM #321
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, CRAM files generated by the CRAM writer containing LZMA-compressed blocks cannot be read correctly by samtools, resulting in an error.
Repro
Cause
According to the CRAM specification, the LZMA compression method used in CRAM is actually based on the XZ format:
In fact, htsjdk uses
XZCompressorOutputStream
/XZCompressorInputStream
from commons-compress when the LZMA method is specified.On the other hand, the current cljam CRAM writer uses
LZMACompressorOutputStream
for LZMA compression. This mismatch causes the generated CRAM files to be unreadable by samtools or htsjdk.Change
The PR replaces the use of
LZMACompressorOutputStream
/LZMACompressorInputStream
withXZCompressorOutputStream
/XZCompressorInputStream
for LZMA compression and decompression.I have confirmed that with this change, CRAM files generated by the CRAM writer containing LZMA-compressed blocks can be successfully read by samtools without errors.