You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Kunal Khatua (JIRA)" <ji...@apache.org> on 2019/01/02 23:01:00 UTC

[jira] [Updated] (DRILL-6050) DRILL-6050: Provide a limit to number of rows fetched for a query in UI

     [ https://issues.apache.org/jira/browse/DRILL-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kunal Khatua updated DRILL-6050:
--------------------------------
    Summary: DRILL-6050: Provide a limit to number of rows fetched for a query in UI  (was: Provide a limit to the number of rows to be fetched for a query submitted via the WebUI)

> DRILL-6050: 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
>            Reporter: Kunal Khatua
>            Assignee: Kunal Khatua
>            Priority: Minor
>             Fix For: 1.16.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)