[
https://issues.apache.org/jira/browse/DRILL-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821461#comment-16821461
]
Bridget Bevens commented on DRILL-6050:
---------------------------------------
Hi [~kkhatua],
I added the info about autoLimit to the following pages:
https://drill.apache.org/docs/planning-and-execution-options/#setting-an-auto-limit-on-the-number-of-rows-returned-for-result-sets
Included a note in the following section about REST client config:
https://drill.apache.org/docs/planning-and-execution-options/#drill-web-ui-row-limit-settings
Added the autoLimit parameter and example here:
https://drill.apache.org/docs/rest-api-introduction/#post-query-json
Added a note to the Limit clause:
https://drill.apache.org/docs/limit-clause/
Please let me know if I need to change anything.
Thanks,
Bridget
> Provide a limit to number of rows fetched for a query in UI
> -----------------------------------------------------------
>
> Key: DRILL-6050
> URL: https://issues.apache.org/jira/browse/DRILL-6050
> Project: Apache Drill
> Issue Type: Improvement
> Components: Web Server
> Reporter: Kunal Khatua
> Assignee: Kunal Khatua
> Priority: Minor
> Labels: doc-impacting, ready-to-commit, user-experience
> Fix For: 1.16.0, 1.17.0
>
>
> Currently, the WebServer side needs to process the entire set of results and
> stream it back to the WebClient.
> Since the WebUI does paginate results, we can load a larger set for
> pagination on the browser client and relieve pressure off the WebServer to
> host all the data.
> e.g. Fetching all rows from a 1Billion records table is impractical and can
> be capped at 10K. Currently, the user has to explicitly specify LIMIT in the
> submitted query.
> An option can be provided in the field to allow for this entry.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
