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 2018/03/20 12:09:00 UTC

[jira] [Commented] (HIVE-18989) Introduce Cap on Number of Session Variables

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

BELUGA BEHR commented on HIVE-18989:
------------------------------------

We should also introduce caps on the length of the variable name and the variable value.

> Introduce Cap on Number of Session Variables
> --------------------------------------------
>
>                 Key: HIVE-18989
>                 URL: https://issues.apache.org/jira/browse/HIVE-18989
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>    Affects Versions: 3.0.0, 2.4.0, 2.3.2
>            Reporter: BELUGA BEHR
>            Priority: Minor
>
> Introduce a cap on the number of session variables a single client can create.
> I am able to create a large file with just "SET" statements and it crashes the HS2 with an OutOfMemory exception.  Because there are no caps, it stores each entry in memory until it finally fails.
> {code}
> SET 6BCF5A44=DF912BD3;
> SET 614DCF23=ABC24816;
> SET B67951D8=DA2645BF;
> SET B9596B09=AB0A2650;
> SET 2D394A85=88968FC9;
> SET 859AD7BE=39710968;
> SET 9ED93926=75996280;
> SET D547BE24=7CF95795;
> SET BB0FB0BF=62DE4A1C;
> SET E447EF3F=858F398F;
> SELECT 1;
> ...
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)