[jira] [Resolved] (CALCITE-555) Differentiate between column not found and ambiguous column exceptions

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

     [ https://issues.apache.org/jira/browse/CALCITE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-555.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

Fixed as part of CALCITE-1208. In {{SqlValidatorTest.checkCustomColumnResolving(String table)}} there is a test:

{code}
    // Fail ambiguous column reference A0, since F1.A0 and F2.A0 both exist with
    // the same resolving priority.
    sql("select ^a0^ from struct." + table)
        .fails("Column 'A0' is ambiguous");
{code}

[~maryannxue], Please let me know if I am mistaken.

> Differentiate between column not found and ambiguous column exceptions
> ----------------------------------------------------------------------
>
>                 Key: CALCITE-555
>                 URL: https://issues.apache.org/jira/browse/CALCITE-555
>             Project: Calcite
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Julian Hyde
>            Priority: Minor
>              Labels: phoenix
>             Fix For: 1.9.0
>
>
> With CALCITE-497, fields within record groups may be referenced through their field names if they're unique. However, there's currently no differentiation between a field/column not being found and a field name being ambiguous. This will likely confuse users, so if possible, these two error conditions should be differentiated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)