[
https://issues.apache.org/jira/browse/CALCITE-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290206#comment-15290206
]
Josh Elser commented on CALCITE-1242:
-------------------------------------
bq. “maximum number of rows for a statement” should be handled inside the SQL
query string.
This is intentionally disjoint. You can push the LIMIT down to the database
already. This is meant to limit the number of results at the JDBC level. For
example, users can limit the number of results you want, while some application
running queries from users can set an upper limit on the number of rows
returned. They have different purposes.
> 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)
