Adding offset to SQL

We're looking to utilize druid to provide raw records and aggregations. While the aggregation portion is working well, we need the offset to be available within SQL in order to continue offering pagination for the raw records.

SQL adding support for OFFSET

Maybe it makes sense to offer OFFSET when pulling back raw data and not offering that as a feature for aggregated data? I assume it makes the implementation that much harder if you have to support aggregations.

The issue provides no file, test, or entry point; begin by locating Druid's SQL parsing and query-planning paths for pagination. Clarify whether OFFSET applies to raw results, aggregations, or both, then add coverage showing the chosen SQL behavior and pagination results.

Written by the indexing model from the issue text.