[HIVE-2155] Improve error messages emitted during semantic analysis

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.8.0
• Hadoop Flags: Reviewed
• Assignee: Syed S. Albiz
• Reporter: Syed S. Albiz
• Created: 09/May/11 23:49
• Updated: 06/Feb/13 09:23
• Resolved: 17/May/11 01:29

Description

Follow-up to HIVE-1731.
A number of issues raised in HIVE-1731 were caused by SemanticAnalyzer not reporting errors correctly.
Specifically, the following issues need to be addressed:

• Line numbers are not always provided and sometimes emitted as (0:-1), which is useless
• Insufficient or unclear context strings are provided

Specific issues described in HIVE-1731:
FAILED: Error in semantic analysis: Schema of both sides of union should match: destinationid:_col1 _col2

• No line/col numbers, context strings provide internal aliases instead of actual column names

FAILED: Error in semantic analysis: line 0:-1 Both Left and Right Aliases Encountered in Join time

• Incorrect line/col number info, no context strings to describe the aliases encountered

FAILED: Error in semantic analysis: AS clause has an invalid number of aliases

• No line/col numbers, not context string to show the aliases encountered

FAILED: Error in semantic analysis: line 1:94 Expression Not In Group By Key a

• testcase: SELECT a.id, VAR(a.cnt) FROM mytable a
• Context string is unhelpful, needs to provide the actual expression, not just the table reference

Issue Links

• is related to: HIVE-3991 junit failure on Semantic Analysis
• is related to: HIVE-1731 Improve miscellaneous error messages