Pagination is currently not supported with group by

Should I file an issue to request support

Sure

Cool. Thanks

You can but note that work done is the same. It’s preferable to do get 1000 rows at once and cache on the client side

Yes, that true for selection as well

True. But those 1K rows have to go over the network

That’s not a lot compared to billions of rows that need to scanned again

Why do you need to scan rows again? you just need to pick from the requested pagination of the ordered results, no?

We don't store cross-query state.

ok

@Kishore G can we use streaming endpoints in selection or group by queries without order by to supports pagination?

I was thinking the same as well.

No, it will use up resources on the Pinot side while we wait for next call

yes, this is the trade off

If we save a state of how many segments processed, that’s the only resource held (and perhaps connection). What else will be held on Pinot side (assuming no ordering)?

you typically need pagination with ordering