Convert LZMA to PARQUET
Turn LZMA archives into PARQUET. The LZMA layer is removed and the bytes inside are written as they were.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop LZMA files on the dialor turn it to pick what to do
The Parquet file that was inside.The LZMA layer comes off and the bytes inside are written as they were.
What you get
One file. The LZMA compression is removed, and what was inside is written out unchanged. Nothing is converted, reshaped or retyped on the way.
The conversion works only when the archive holds Parquet data. You ask for the format you know is inside, and the result is that data as it was stored.
What is refused
Anything else is refused. If the file inside the LZMA archive is not Parquet, the conversion does not turn it into Parquet. It does not read rows from a CSV or other data and build columns from them.
There are no options to set. The conversion takes the LZMA file and gives back the one file inside it.
Next steps
Once you have the Parquet file, merge PARQUET joins several of them. For other routes from LZMA, see every LZMA conversion.
LZMA and PARQUET.What each format is.
The formats
LZMA
A single file compressed with the legacy LZMA format that xz replaced.
- Extensions
- .lzma
- MIME type
- application
/x -lzma - Kind
- Archives
Parquet
The columnar data format of analytics. Compressed, typed and fast to scan.
- Extensions
- .parquet .pq
- MIME type
- application
/vnd .apache .parquet - Kind
- Text and data
In your code.The same LZMA to PARQUET conversion through the API, for your app or your agent.
$ cv convert archive.lzma archive.parquet$ cv convert archive.lzma archive.parquetQuestions.What people ask about LZMA to PARQUET.
No. The LZMA file must hold Parquet data already. Anything else is refused.
No. The LZMA layer is removed and the bytes inside are written as they were.
One file.
No. This conversion has no options.