neat. i'm pretty novice in the guts of this kind of stuff, but how does this work under the hood for blocking operators where they "cannot output a single row until the last row of their input has been seen"?

i think this is where spark shuffling comes in? but how does it work here.

https://duckdb.org/docs/stable/guides/performance/how_to_tun...

In my experience ray clusters don't scale well and end up costing you more money. You need to run permanent per-user instances etc.

What you need is a multi-tenancy shared infrastructure that is elastic.

feels like a missed opportunity to call it cluster-quack xD