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

Improve error message when table or column not found

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.12.0
    • 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

          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

          Improvement - An improvement or enhancement to an existing feature or task. CALCITE-6539 Improve error messages due to misspellings using (say) Levenshtein distance

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. CALCITE-4653 Improve exception message when identifiers using reserved keyword

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: