[CALCITE-1549] Improve error message when table or column not found

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.12.0
• Assignee: Julian Hyde
• Reporter: Julian Hyde
• Created: 21/Dec/16 22:33
• Updated: 24/Mar/17 03:20
• Resolved: 13/Jan/17 19:29

Description

When a table is not found in a query, the current message makes it difficult to tell among several possibilities: the schema was incorrect, the schema was correct but had wrong case, the table was incorrect, the table was correct but had wrong case. Given a query, say

select * from schema1.table1, schema2.table2, table3

we should give an error that discriminates between those possibilities for "schema1.table1", and also for "table3" looking in the default schema.

Issue Links

• is related to: PHOENIX-3635 Many tests failing for not resolving table name properly in Phoenix-Calcite