clintropolis commented on a change in pull request #10235:
URL: https://github.com/apache/druid/pull/10235#discussion_r466009628
##########
File path: docs/querying/limitspec.md
##########
@@ -35,11 +35,23 @@ The default limit spec takes a limit and the list of
columns to do an orderBy op
```json
{
"type" : "default",
- "limit" : <integer_value>,
- "columns" : [list of OrderByColumnSpec],
+ "limit" : <optional integer>,
+ "offset" : <optional integer>,
+ "columns" : [<optional list of OrderByColumnSpec>],
}
```
+The "limit" parameter is the maximum number of rows to return.
+
+The "offset" parameter tells Druid to skip this many rows when returning
results. If both "limit" and "offset" are
+provided, then "offset" will be applied first, followed by "limit". For
example, a spec with limit 100 and offset 10
+will return 100 rows starting from row number 10. Skipped rows will still need
to be generated internally and then
+discarded, meaning that raising offsets to high values can cause queries to
use additional resources.
Review comment:
sgtm :+1:
----------------------------------------------------------------
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]
