[ 
https://issues.apache.org/jira/browse/DRILL-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835203#comment-16835203
 ] 

Bridget Bevens edited comment on DRILL-7048 at 5/7/19 11:59 PM:
----------------------------------------------------------------

Hi [~kkhatua],

I've updated the following page with info about setMaxRows:
https://drill.apache.org/docs/using-the-jdbc-driver/#using-the-drill-driver-class-name
 

Also included it in the Note in this section:
https://drill.apache.org/docs/planning-and-execution-options/#drill-web-ui-row-limit-settings
 

Let me know if I need to make any changes. 

Thanks,
Bridget


was (Author: bbevens):
Hi [~kkhatua],

I've updated the following page with info about setMaxRows:
https://drill.apache.org/docs/using-the-jdbc-driver/#using-the-drill-driver-class-name
 

Also included it in the Note in this section:
https://drill.apache.org/docs/planning-and-execution-options/#drill-web-ui-row-limit-settings
 

Let me know if I need to make any changes. 

Thanks,
Bridget

> Implement JDBC Statement.setMaxRows() with System Option
> --------------------------------------------------------
>
>                 Key: DRILL-7048
>                 URL: https://issues.apache.org/jira/browse/DRILL-7048
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components: Client - JDBC, Query Planning & Optimization
>    Affects Versions: 1.16.0
>            Reporter: Kunal Khatua
>            Assignee: Kunal Khatua
>            Priority: Major
>              Labels: doc-impacting, ready-to-commit
>             Fix For: 1.16.0
>
>
> With DRILL-6960, the webUI will get an auto-limit on the number of results 
> fetched.
> Since more of the plumbing is already there, it makes sense to provide the 
> same for the JDBC client.
> In addition, it would be nice if the Server can have a pre-defined value as 
> well (default 0; i.e. no limit) so that an _admin_ would be able to ensure a 
> max limit on the resultset size as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to