[
https://issues.apache.org/jira/browse/CALCITE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626710#comment-17626710
]
Julian Hyde commented on CALCITE-2322:
--------------------------------------
[~zabetak], If you have time, could you get this PR into a state you are happy
with and merge it? I think that it's more important to merge this PR than to
get it perfect to everyone's satisfaction.
I now think {{fetch_size}} is a good name. JDK has a method
{{ResultSet.setFetchSize(int rows)}}, so it is clear that {{fetch_size}} refers
to rows. I would also accept whatever name [~zabetak] decides. I apologize for
my bike-shedding on 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: avatica, core
> Affects Versions: 1.11.0
> Reporter: Kevin Minder
> Priority: Major
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
