[
https://issues.apache.org/jira/browse/CALCITE-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370941#comment-17370941
]
Julian Hyde commented on CALCITE-2322:
--------------------------------------
Sorry, cancel that. I didn't read the context.
I think the property should be called "fetch_row_count":
* not "fetch_size" (because that implies bytes, not rows);
* not "default_fetch_row_count" (because it is understood that this is a
default that can be overridden per-statement; furthermore, there is a default
default, which is 100);
* not "fetchRowCount" (because Avatica uses snake_case, even though Calcite
uses lowerCamelCase).
Please add the new property to [Avatica client
reference.|https://calcite.apache.org/avatica/docs/client_reference.html]
Re. camel vs. snake. I'll log a separate Jira case to allow properties to be
specified in any form - UPPER_SNAKE or lower_snake or lowerCamel or UpperCamel.
For now, stick with Avatica's house style, which is lower_snake.
> 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: 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.3.4#803005)
