Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
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.
Attachments
Issue Links
- is related to
-
PHOENIX-3635 Many tests failing for not resolving table name properly in Phoenix-Calcite
-
- Open
-