[jira] [Comment Edited] (CALCITE-1549) Improve error message when table or column not found

["Julian Hyde (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15843317#comment-15843317 ] 

Julian Hyde edited comment on CALCITE-1549 at 1/27/17 6:52 PM:
---------------------------------------------------------------

I don't fully understand PHOENIX-3635 but it looks as this case changed some assumptions that Phoenix was relying on but is not a "bad" change overall. If I am mistaken, and we need to change Calcite again, please let me know.


was (Author: julianhyde):
I don't fully understand PHOENIX-3635 but it looks as this case changed some assumptions but is not a "bad" change overall. If I am mistaken, and we need to change Calcite again, please let me know.

> Improve error message when table or column not found
> ----------------------------------------------------
>
>                 Key: CALCITE-1549
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1549
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>             Fix For: 1.12.0
>
>
> 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
> {code}
> select * from schema1.table1, schema2.table2, table3
> {code}
> we should give an error that discriminates between those possibilities for "schema1.table1", and also for "table3" looking in the default schema.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)