[
https://issues.apache.org/jira/browse/CALCITE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486585#comment-16486585
]
ASF GitHub Bot commented on CALCITE-2322:
-----------------------------------------
GitHub user kminder opened a pull request:
https://github.com/apache/calcite-avatica/pull/49
CALCITE-2322: Add fetch size support to connection url and JDBC state…
Adds the support for both a URL connection param fetch_size and the JDBD
Statement API setFetchSize. This can be used to tune performance for queries
that return a large number of rows.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kminder/calcite-avatica
calcite-2322_add-fetch-size-support-to-connection-url-and-jdbc-statement
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/calcite-avatica/pull/49.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #49
----
commit c67cd9ac190532e7255b7936812665999b6e334f
Author: Kevin Minder <kevin.minder@...>
Date: 2018-05-23T01:46:23Z
CALCITE-2322: Add fetch size support to connection url and JDBC statement
----
> Add fetch size support to connection url and JDBC statement
> -----------------------------------------------------------
>
> Key: CALCITE-2322
> URL: https://issues.apache.org/jira/browse/CALCITE-2322
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.11.0
> Reporter: Kevin Minder
> Assignee: Julian Hyde
> Priority: Major
> Attachments: CALCITE-2322.patch
>
>
> Currently the remote driver defaults to hard coded fetch size of 100 rows.
> When a connection is operating in HTTP mode having such a small fetch size
> can add enormous overhead. This is especially true if TLS connections are
> used and made worse if each connection flows throw multiple proxies.
> Consider that 100K rows returned 100 rows at a time will make 1K HTTP POST
> requests. One might say that nobody should ever do that but some tools like
> Spotfire may end up doing this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
