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

Posted to issues@drill.apache.org by "Volodymyr Vysotskyi (JIRA)" <ji...@apache.org> on 2019/04/04 17:52:00 UTC

[jira] [Updated] (DRILL-7048) Implement JDBC Statement.setMaxRows() with System Option

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

Volodymyr Vysotskyi updated DRILL-7048:
---------------------------------------
    Labels: doc-impacting ready-to-commit  (was: doc-impacting)

> 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 &amp; Optimization
>    Affects Versions: 1.15.0
>            Reporter: Kunal Khatua
>            Assignee: Kunal Khatua
>            Priority: Major
>              Labels: doc-impacting, ready-to-commit
>             Fix For: 1.17.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)