[
https://issues.apache.org/jira/browse/CALCITE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371594#comment-17371594
]
Vladimir Sitnikov edited comment on CALCITE-2322 at 6/29/21, 7:22 PM:
----------------------------------------------------------------------
Just in case, I think {{(default_)fetch_size_rows}} and
{{(default_)fetch_size_bytes}} are more consistent (and they are consistent
with {{setFetchSize}} JDBC API name) than {{fetch_row_count}} and
{{fetch_byte_count}} (?) {{fetch_bytes}} (?). I don't really know how to add a
byte-sized property side by side with {{fetch_row_count}}.
Julian asked for a byte-size property in 2018
(https://issues.apache.org/jira/browse/CALCITE-2322?focusedCommentId=16484416&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16484416),
and I missed the comments completely.
was (Author: vladimirsitnikov):
Just in case, I think {{(default_)fetch_size_rows}} and
{{(default_)fetch_size_bytes}} are more consistent than {{fetch_row_count}} and
{{fetch_byte_count}} (?) {{fetch_bytes}} (?). I don't really know how to add a
byte-sized property side by side with {{fetch_row_count}}.
Julian asked for a byte-size property in 2018
(https://issues.apache.org/jira/browse/CALCITE-2322?focusedCommentId=16484416&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16484416),
and I missed the comments completely.
> 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)
