[
https://issues.apache.org/jira/browse/CALCITE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484416#comment-16484416
]
Julian Hyde commented on CALCITE-2322:
--------------------------------------
We prefer pull requests to patches, if you don't mind.
What are your thoughts on also having a fetch-bytes parameter? (Not necessarily
as part of this change.) It's frustrating that ODBC and JDBC specify row
counts, whereas all of the infrastructure between client and server (fixed-size
buffer, MTU) cares about byte counts. Mapping between the two is not
straightforward because we don't always have good estimates for row width.
> 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)
