Programming

17513 readers

243 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

parquet vs csv (lemmy.ml)

submitted 2 months ago by [email protected] to c/programming

19 comments fedilink hide all child comments

What's your take on parquet?

I'm still reading into it. Why is it closely related to apache? Does inly apache push it? Meaning, if apache drops it, there'd be no interest from others to push it further?

It's published under apache hadoop license. It is a permissive license. Is there a drawback to the license?

Do you use it? When?

I assume for sharing small data, csv is sufficient. Also, I assume csv is more accessible than parquet.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 2 months ago (2 children)

How does this differ from graphQL?

[–] [email protected] 5 points 2 months ago (1 children)

Graphql is a protocol for interacting with a remote system, parquet is about having a local file that you can index and retrieve data from in a more efficient way. It's especially useful when the data has a fairly well defined structure but may be large enough that you can't or don't want to bring it all into memory. They're similar concepts, but different applications

[–] [email protected] 3 points 2 months ago

Thank you!

[–] [email protected] 4 points 2 months ago

Parquet is a storage format; graphQL is a query language/transmission strategy.