Re:Show HN: ZSV (Zip Separated Values) columnar data format
by orthoxerox on Saturday April 13, 2024 @06:35PM
(#40026806)
I was comparing it with Parquet, which is much more complex, but has features that help you access the data in less than O(n), like row groups and pages.
Re:Show HN: ZSV (Zip Separated Values) columnar data format
by cm2187 on Saturday April 13, 2024 @09:12PM
(#40027810)
you mentioned NLJSON and CSV, which would require to read all columns from the disk.
Re:Show HN: ZSV (Zip Separated Values) columnar data format
by orthoxerox on Sunday April 14, 2024 @03:44AM
(#40029427)
Yes, but you would usually have to read at least two columns anyway. What are the datasets that are too large to be ingested completely, but too small for a proper columnar format?
If ZSV is meant to occupy the gap between CSV/NLJSON (smaller datasets) and Parquet/DuckDB (larger datasets), this niche is actually really small, if not nonexistent.
Re:Show HN: ZSV (Zip Separated Values) columnar data format
by cm2187 on Sunday April 14, 2024 @04:13AM
(#40029557)
yes it's unclear to me what is the advantage over parquet with compression. And there are enough file formats flying around already.
Re:Show HN: ZSV (Zip Separated Values) columnar data format
by makmanalp on Saturday April 13, 2024 @09:22PM
(#40027865)
Even with an OLAP use case, you're most often not scanning every row in the database if you even have a single where clause / conditional filter which is almost always. You need to have some level of locality and if your format doesn't support that, that'll be enough to kill performance.
Also parquet has lots of features that'll get you to the general vicinity of a single record tolerably fast without sacrificing much in terms of storage or computational complexity. It's a small price for a big win.
The price you pay is that it is inefficient for single record access, or for "select * " kind of queries.