Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-1549

Improve error message when table or column not found

          Details

          • Type: Bug
          • Status: Closed
          • Priority: Major
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: 1.12.0
          • Component/s: None
          • Labels:
            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

                Sub-task - The sub-task of the issue PHOENIX-3635 Many tests failing for not resolving table name properly in Phoenix-Calcite

                • Major - Major loss of function.
                • Open

                  Activity

                    People

                    • Assignee:
                      julianhyde Julian Hyde
                      Reporter:
                      julianhyde Julian Hyde
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      3 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: