Convert LZ to JSONL
Turn LZ archives into JSONL. The lzip layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop LZ files on the dialor turn it to pick what to do
The JSONL inside, taken out of the LZ.The lzip layer is removed and the bytes inside are written as they were.
What you get
One JSONL file. The lzip compression is taken off, and the content inside is written out unchanged, so every line is exactly as it was before it was compressed.
What you need to know
Ask for the format you know is inside the LZ file. If you ask for anything else, the conversion is refused. An LZ file that holds something other than JSON Lines is not turned into JSONL.
The conversion has no options. It removes the lzip layer and does nothing more to the content.
When it stops
The conversion stops with
input_corruptedwhen the file could not be parsed. It stops withunsupported_elementswhen the file holds something the target cannot carry, or when some inputs cannot become the format the join takes.To go the other way, use JSONL to LZ.
LZ and JSONL.What each format is.
The formats
Lzip
A single file compressed with lzip, an LZMA format built for long-term archiving.
- Extensions
- .lz
- MIME type
- application
/x -lzip - 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 LZ to JSONL conversion through the API, for your app or your agent.
$ cv convert archive.lz archive.jsonl$ cv convert archive.lz archive.jsonlQuestions.What people ask about LZ to JSONL.
No. The bytes inside the LZ file are written as they were, so the lines are not rewritten.
The conversion is refused. Ask for the format you know is inside.
No. It has no options.
It means the file could not be parsed. The conversion stops with input_corrupted when that happens.