[
https://issues.apache.org/jira/browse/HIVE-13645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267301#comment-15267301
]
Sushanth Sowmyan commented on HIVE-13645:
-----------------------------------------
[~sershe], Is branch-2.0 okay for commits right now, or should we hold off?
> 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)
