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

Posted to issues@hive.apache.org by "Sushanth Sowmyan (JIRA)" <ji...@apache.org> on 2016/04/28 21:45:13 UTC

[jira] [Commented] (HIVE-13645) Beeline needs null-guard around hiveVars and hiveConfVars read

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

Sushanth Sowmyan commented on HIVE-13645:
-----------------------------------------

[~thejas], could you please take a look - this is a near-trivial patch.

> Beeline needs null-guard around hiveVars and hiveConfVars read
> --------------------------------------------------------------
>
>                 Key: HIVE-13645
>                 URL: https://issues.apache.org/jira/browse/HIVE-13645
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>    Affects Versions: 2.1.0
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
>         Attachments: HIVE-13645.patch
>
>
> Beeline has a bug wherein if a user does a !save ever, then on next load, if beeline.hiveVariables or beeline.hiveconfvariables are empty, i.e. \{\} or unspecified, then it loads it as null, and then, on next connect, there is no null-check on these variables leading to an NPE.  



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