Convert BZ2 to JSONL
Turn BZ2 archives into JSONL. The bzip2 layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop BZ2 files on the dialor turn it to pick what to do
The JSON Lines inside your BZ2 file.The bzip2 layer comes off and the lines inside are written as they were.
What you get
One JSONL file. The bzip2 layer is removed and the bytes inside are written out unchanged, so the content is the same as before it was compressed.
Nothing is parsed, reordered or rewritten along the way. The file works as JSONL only if it was JSONL when it was compressed.
Ask for what is inside
Choose JSONL only when you know the BZ2 file holds JSON Lines. Any other format is refused, so the target has to match the contents.
A BZ2 file holds a single file, and the result is one file.
When it stops
The conversion stops with
input_corruptedwhen the file could not be parsed. It stops withunsupported_elementswhen the file holds something JSONL cannot carry, or when some inputs cannot become the format the join takes.To go the other way, use JSONL to BZ2.
BZ2 and JSONL.What each format is.
The formats
Bzip2
A single file compressed with bzip2.
- Extensions
- .bz2
- MIME type
- application
/x -bzip2 - Kind
- Archives
JSON Lines
JSON Lines, one JSON object per line, the format of logs and datasets.
- Extensions
- .jsonl .ndjson
- MIME type
- application
/jsonl - Kind
- Text and data
In your code.The same BZ2 to JSONL conversion through the API, for your app or your agent.
$ cv convert archive.bz2 archive.jsonl$ cv convert archive.bz2 archive.jsonlQuestions.What people ask about BZ2 to JSONL.
No. The bytes inside the archive are written as they were. Only the bzip2 layer is removed.
The conversion is refused. Ask for the format you know is inside the BZ2 file.
The file could not be parsed. The conversion stops at that point.
Yes. JSONL to BZ2 does the reverse.