You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Vaibhav Gumashta (JIRA)" <ji...@apache.org> on 2016/10/06 07:57:20 UTC

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

Vaibhav Gumashta created HIVE-14901:
---------------------------------------

             Summary: HiveServer2: Use user supplied fetch size to determine #rows serialized in tasks
                 Key: HIVE-14901
                 URL: https://issues.apache.org/jira/browse/HIVE-14901
             Project: Hive
          Issue Type: Sub-task
            Reporter: Vaibhav Gumashta


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. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)