[HIVE-13645] Beeline needs null-guard around hiveVars and hiveConfVars read

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 1.2.2, 1.3.0, 2.0.1, 2.1.0
• Component/s: Beeline
• Target Version/s: 2.1.0
• Assignee: Sushanth Sowmyan
• Reporter: Sushanth Sowmyan
• Created: 28/Apr/16 19:42
• Updated: 21/Jun/16 15:10
• Resolved: 02/May/16 19:12

Description

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.