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

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Component/s: HiveServer2, JDBC, ODBC
• Labels: TODOC2.2
• Target Version/s: 2.2.0
• Assignee: Norris Lee
• Reporter: Vaibhav Gumashta
• Created: 06/Oct/16 07:57
• Updated: 07/Mar/17 07:43
• Resolved: 06/Mar/17 22:28

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.

Issue Links

• is related to: HIVE-14876 make the number of rows to fetch from various HS2 clients/servers configurable