|
|
|
|
|
by CharlesW
1284 days ago
|
|
> It's so complex to work with, that unless you're specifically in data science, it's both unheard of and unusable. FWIW, in my experience at a "data analytics platform" company, it's reasonably popular for data-heavy workflows since Parquet is well-defined, and file sizes (especially as the amount of data grows) are a fraction of their CSV equivalents. > Is it a limitation of the format itself? I don't think so. In other languages, you can generally read/write Parquet files without a ton of dependencies (e.g. https://github.com/xitongsys/parquet-go). |
|