You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Kevin Minder (JIRA)" <ji...@apache.org> on 2018/05/22 18:47:00 UTC
[jira] [Commented] (CALCITE-2322) Add fetch size support to
connection url and JDBC statement
[ https://issues.apache.org/jira/browse/CALCITE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484409#comment-16484409 ]
Kevin Minder commented on CALCITE-2322:
---------------------------------------
I'll have to review your development workflow but I've attached a patch that implements this.
> 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-avatica.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)