Daniel Barclay (Drill) created DRILL-3812:
---------------------------------------------
Summary: message for invalid compound name doesn't identify part
that's bad
Key: DRILL-3812
URL: https://issues.apache.org/jira/browse/DRILL-3812
Project: Apache Drill
Issue Type: Bug
Components: SQL Parser
Reporter: Daniel Barclay (Drill)
Assignee: Aman Sinha
When a compound name (e.g., {{schema.subschema.table}}) is invalid, the error
message doesn't where it went bad (e.g., which part referred to something
unknown and/or non-existent). For example, see the query and the "VALIDATION
ERROR ..." line in the following:
{noformat}
0: jdbc:drill:zk=local> SELECT * FROM `dfs.NoSuchSchema`.`empty_directory`;
Sep 20, 2015 10:38:24 PM org.apache.calcite.sql.validate.SqlValidatorException
<init>
SEVERE: org.apache.calcite.sql.validate.SqlValidatorException: Table
'dfs.NoSuchSchema.empty_directory' not found
Sep 20, 2015 10:38:24 PM org.apache.calcite.runtime.CalciteException <init>
SEVERE: org.apache.calcite.runtime.CalciteContextException: From line 1, column
15 to line 1, column 32: Table 'dfs.NoSuchSchema.empty_directory' not found
Error: VALIDATION ERROR: From line 1, column 15 to line 1, column 32: Table
'dfs.NoSuchSchema.empty_directory' not found
[Error Id: 2a298c8e-2923-4744-8f78-b0cf36c83799 on dev-linux2:31010]
(state=,code=0)
{noformat}
A better error message would say that {{dfs.NoSuchSchema}} was not found (or
that no {{NoSuchSchema}} was found in schema {{dfs}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
