[ https://issues.apache.org/jira/browse/CALCITE-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290034#comment-15290034 ]
Duo Xu commented on CALCITE-1242: --------------------------------- or avoid confusion, maxRowCount should only be translated to “number of rows per frame”, “maximum number of rows for a statement” should be handled inside the SQL query string. > 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)