[
https://issues.apache.org/jira/browse/CALCITE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371499#comment-17371499
]
Vladimir Sitnikov edited comment on CALCITE-2322 at 6/29/21, 3:50 PM:
----------------------------------------------------------------------
"fetch_row_count" implies that Avatica would **always** use the given row
count. That is too restrictive, and it creates ambiguities: "what if I specify
fetch_row_count both at connection and at the statement level?"
"default_fetch_row_count" makes perfect sense for the connection property: it
tells the connection which value to start with, and then the implementation
should be free to adjust it (e.g. the implementation could use dynamic fetch
size if it wants).
was (Author: vladimirsitnikov):
"fetch_row_count" implies that Avatica would **always** use the given row
count. That is too restrictive, and it creates ambiguities: "what if I specify
fetch_row_count both at connection and at the statement level?"
"default_fetch_row_count" makes perfect sense for the connection property: it
tells the connection which value to start with, and then the implementation
should be free to adjust it.
> 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: 2h 40m
> 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.3.4#803005)
