[HIVE-14901] HiveServer2: Use user supplied fetch size to determine #rows serialized in tasks - ASF JIRA

Log work

Agile Board

Rank to Top

Rank to Bottom

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Convert to Issue

Move

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Sub-task
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 2.1.0
Fix Version/s: None
Component/s: HiveServer2, JDBC, ODBC
Labels:
- TODOC2.2

Target Version/s:

2.2.0

Description

Currently, we use hive.server2.thrift.resultset.max.fetch.size to decide the max number of rows that we write in tasks. However, we should ideally use the user supplied value (which can be extracted from the ThriftCLIService.FetchResults' request parameter) to decide how many rows to serialize in a blob in the tasks. We should however use hive.server2.thrift.resultset.max.fetch.size to have an upper bound on it, so that we don't go OOM in tasks and HS2.