hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Mollitor (Jira)" <>
Subject [jira] [Commented] (HIVE-23005) Consider Default JDBC Fetch Size From HS2
Date Sat, 21 Mar 2020 01:09:00 GMT


David Mollitor commented on HIVE-23005:

[~ngangam] OK.  Guava removed from JDBC project.  [^HIVE-23005.6.patch]   Thanks for your
time on the review.

> Consider Default JDBC Fetch Size From HS2
> -----------------------------------------
>                 Key: HIVE-23005
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: JDBC
>            Reporter: David Mollitor
>            Assignee: David Mollitor
>            Priority: Major
>         Attachments: HIVE-23005.1.patch, HIVE-23005.2.patch, HIVE-23005.3.patch, HIVE-23005.4.patch,
HIVE-23005.5.patch, HIVE-23005.6.patch
> # Create two fetch sizes: and "init" fetch size and a "default" fetch size. The "init"
fetch size comes from the JDBC connection string _fetchSize_ (if present) and the "default"
fetch size comes from _HIVE_SERVER2_THRIFT_RESULTSET_DEFAULT_FETCH_SIZE_ the server response
to the open session request.
>  # When a {{Statement}} is created, its starting fetch size is the "init" fetch size
(may be 0)
>  # Manually setting the fetch size on the {{Statement}} to 0, sets the fetch size to
be the server default
> Setting to zero defaults to the server's instructed default and adheres to: 
> bq. If the value specified is zero, then the hint is ignored. The default value is zero.
> That is to say, if the fetch size is 0, the default from the server is used, otherwise
the user can pass a 'hint' and that will be the number of rows fetched instead.

This message was sent by Atlassian Jira

View raw message