You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Vaibhav Gumashta (JIRA)" <ji...@apache.org> on 2016/08/16 19:22:20 UTC

[jira] [Updated] (HIVE-12427) HiveServer2: Improve HiveServer2 JDBC/ODBC ResultSet performance - part1

     [ https://issues.apache.org/jira/browse/HIVE-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vaibhav Gumashta updated HIVE-12427:
------------------------------------
    Summary: HiveServer2: Improve HiveServer2 JDBC/ODBC ResultSet performance - part1  (was: HiveServer2: Improve HiveServer2 JDBC/ODBC ResultSet performance)

> HiveServer2: Improve HiveServer2 JDBC/ODBC ResultSet performance - part1
> ------------------------------------------------------------------------
>
>                 Key: HIVE-12427
>                 URL: https://issues.apache.org/jira/browse/HIVE-12427
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2, JDBC, ODBC
>            Reporter: Vaibhav Gumashta
>
> The current implementation does a lot of CPU intensive work in HiveServer2. It deserializes the temporary results written to disk  and also serializes the results into thrift objects in HS2. This adds to the latency of fetching results via HS2. Doing that work in the task nodes would get that work done in parallel and scale it, thereby reducing the time it takes to retrieve large results.



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