[
https://issues.apache.org/jira/browse/CALCITE-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290030#comment-15290030
]
Duo Xu commented on CALCITE-1242:
---------------------------------
I would suggest we expose two parameters instead of a single "maxRowCount".
“maximum number of rows for a statement”: this is equivalent to "limit" in sql,
“number of rows per frame”: this is equivalent to "how many rows it returns in
single http call"
Currently maxRowCount is mixed with these two.
> Allow configuration of maximum allowed value for maxRowCount
> ------------------------------------------------------------
>
> Key: CALCITE-1242
> URL: https://issues.apache.org/jira/browse/CALCITE-1242
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Duo Xu
> Assignee: Josh Elser
> Fix For: avatica-1.9.0
>
>
> There are several APIs having the maxRowCount parameter. Currently this
> setting is hard coded in Avatica as 100. So if the user set maxRowCount > 100
> in PrepareAndExecuteRequest, for example, the server will still only return
> 100 results. So the APIs are currently broken.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
