[
https://issues.apache.org/jira/browse/CALCITE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529834#comment-14529834
]
Xavier FH Leong edited comment on CALCITE-712 at 5/6/15 3:49 AM:
-----------------------------------------------------------------
Using re-executing prepare method, new commit at:
https://github.com/xhoong/incubator-calcite/commit/48324c8da810963d9852887dd7e7e2a3f3e8faa0
As you can see, can be quite flaky calling meta.prepare 2x at remote and at
local when there's a setMaxRows
was (Author: xhoong):
Using re-executing prepare method, new commit at:
https://github.com/xhoong/incubator-calcite/commit/fe143af3b54abebabb27ab2397526eee966f1f5d
As you can see, can be quite flaky calling meta.prepare 2x at remote and at
local when there's a setMaxRows
> 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)
