I think "may not be super straightforward" undersells the learning curve here. I took to SQL pretty naturally but gnarly partitioning is still the easiest way for me to get tripped up. Having taught a lot of data sciencey folks advanced SQL, even simple uses of partitioning tend to be a big barrier compared to what comes before.
Totally understand the concern, for now, it’s just for a particular datatype, all of the other operations are happening normally inside your query and you can still use window functions...
And btw, I love window functions and will probably be doing a post on them, but they can be a little bit weird and have some really odd ordering properties with aggregates etc.
The point of this is really much more about providing choices for folks. But yeah, if we find that people are just getting really confused we could re-consider, that’s part of why we released it experimentally.
We're planning on providing various outputs, json is definitely one format we'd want to support, want to file a github issue with the layout that you'd want and we can start getting some feedback to implement?