[
https://issues.apache.org/jira/browse/CALCITE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533762#comment-14533762
]
Xavier FH Leong commented on CALCITE-712:
-----------------------------------------
We have user on squirrel executing a query on a large table without SQL limit,
by default squirrel apply row limit of 100. The problem lies in when user fire
that query, the server side will assemble the whole result set before sending
it over (which is millions of rows), and it choke.
So there's 2 issue, the limit set by squirrel is not fulfilled. And the fetch
is not working for Statement.execute() (it's working for PreparedStatement for
now). Need another JIRA to capture the fetch deficiency in Statement.execute()
> Avatica statement execute return all resultset instead of MaxRows from
> setMaxRows
> ---------------------------------------------------------------------------------
>
> Key: CALCITE-712
> URL: https://issues.apache.org/jira/browse/CALCITE-712
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.3.0-incubating
> Reporter: Xavier FH Leong
> Assignee: Julian Hyde
> Labels: avatica
>
> setMaxRows is supported, but after moving to JdbcMeta, max row was ignore and
> full result set is return instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
