abhishekrb19 commented on pull request #10233: URL: https://github.com/apache/druid/pull/10233#issuecomment-668245599
> I was thinking of starting with Scan and GroupBy. Timeseries could make sense too. TopN, I'm not as sure about, because the fact that offset needs to bump up limit means that it will start to increase memory use pretty quickly as you go to the later pages. @gianm, yes, that makes sense. Also, I was wondering if in the future we could have a stateful offset implementation where the broker could cache the query/result set from a previous request for a short duration. This could potentially be leveraged in subsequent requests without having to look at the entire result set every time and throw away the rows that are not needed. I think this could get tricky for identical rows, but would be computationally _less_ resource intensive? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
