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/05/02 21:13:12 UTC

[jira] [Updated] (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:all-tabpanel ]

Sushanth Sowmyan updated HIVE-13645:
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0
                   1.2.2
                   1.3.0
           Status: Resolved  (was: Patch Available)

> 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
>            Priority: Minor
>             Fix For: 1.3.0, 1.2.2, 2.1.0
>
>         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)