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

Posted to issues@hive.apache.org by "BELUGA BEHR (JIRA)" <ji...@apache.org> on 2017/05/12 20:23:04 UTC

[jira] [Commented] (HIVE-16663) String Caching For Rows

    [ https://issues.apache.org/jira/browse/HIVE-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008655#comment-16008655 ] 

BELUGA BEHR commented on HIVE-16663:
------------------------------------

Understanding that one can also set "incremental" for beeline.  This patch is to assist in alleviating the following:

Setting --incremental=true is recommended if you encounter an OutOfMemory on the client side (due to the fetched result set size being large).

> String Caching For Rows
> -----------------------
>
>                 Key: HIVE-16663
>                 URL: https://issues.apache.org/jira/browse/HIVE-16663
>             Project: Hive
>          Issue Type: Improvement
>          Components: Beeline
>    Affects Versions: 2.0.1
>            Reporter: BELUGA BEHR
>            Priority: Minor
>         Attachments: HIVE-16663.1.patch, HIVE-16663.2.patch
>
>
> It is very common that there are many repeated values in the result set of a query.  As it currently stands, beeline does not attempt to cache any of these values and therefore it consumes a lot of memory.
> Adding a string cache may save a lot of memory.  There are organizations that use beeline to perform ETL processing of result sets into CSV.  This will better support those organizations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)