[
https://issues.apache.org/jira/browse/CALCITE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539170#comment-14539170
]
Xavier FH Leong commented on CALCITE-712:
-----------------------------------------
I still think that the consistency within Avatica will be beneficial, if not,
care needs to be in for special handling (as you pointed out earlier)
Finalize commit:
https://github.com/xhoong/incubator-calcite/commit/e644a3ad8344f68e114da0adf60f41a227b2aff9
Added a test in CalciteRemoteDriverTest.
My 2 cent is to have the interface supporting JDBC consistent with JDBC,
extending the interface to support other use case if needed (where there's a
use case calling for 0 row ResultSet)
> 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
> Fix For: next
>
>
> 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)
