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

Posted to issues@calcite.apache.org by "Xavier FH Leong (JIRA)" <ji...@apache.org> on 2015/06/03 02:48:50 UTC

[jira] [Issue Comment Deleted] (CALCITE-718) Enable fetch to work for Statement.execute()

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

Xavier FH Leong updated CALCITE-718:
------------------------------------
    Comment: was deleted

(was: Replied to your comments.

As for test case, when I was doing it, the existing test able to cover as it catches all the logic that I did not convert. As the fetch is internal logic, the front end logic test case tested the functionality once you convert from non-fetch to fetch.

)

> Enable fetch to work for Statement.execute()
> --------------------------------------------
>
>                 Key: CALCITE-718
>                 URL: https://issues.apache.org/jira/browse/CALCITE-718
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Xavier FH Leong
>            Assignee: Julian Hyde
>            Priority: Minor
>              Labels: avatica
>
> Current Avatica Statement.execute() will build the complete result set before sending back to client, enable fetch to send only max fetch rows.
> Reference discussion: CALCITE-712



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)