Re:Querying Parquet with Precision Using DuckDB
by wenc on Friday June 25, 2021 @08:05PM
(#27637749)
That's a fair question, and I guess my answer would be "ergonomics". I tend to work in Python not Scala, and there's a certain amount of boilerplate that is necessary to even get Spark functional. For instance, this is a code snippet to spin up local Spark (not Spark Shell) I have stored in a file which I have to look up because there's no way I can commit this to memory:
Not to mention fussy things you have to do in Spark to alias a table:
Compare this to these 2 (!) DuckDB commands in the Python REPL that I just ran moments ago:
[ Parent
| on HN ]
Re:Querying Parquet with Precision Using DuckDB
by nyokodo on Friday June 25, 2021 @09:51PM
(#27638331)
> I tend to work in Python not Scala
Fair enough. Iām more comfortable in Scala than Python. Have you tried using a local Jupyter notebook? That would seem to tick all the boxes. https://jupyter.org/install
Re:Querying Parquet with Precision Using DuckDB
by wenc on Friday June 25, 2021 @10:10PM
(#27638426)
I do use Jupyter and the boilerplate code above is what I usually deploy in Jupyter.
Spark syntax is still just a touch more complicated than necessary for my needs because it's solving the much more general distributed computing problem. (not to mention the impedance mismatch -- Spark is very much a Scala native app, and it feels that way to a Python user).
DuckDB on the other hand seems to provide a quick way to interact with local Parquet files in Python, which I appreciate.