drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Barclay (Drill) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-2880) non-syntax error has unexpected category "PARSE ERROR"
Date Sun, 26 Apr 2015 06:01:38 GMT
Daniel Barclay (Drill) created DRILL-2880:
---------------------------------------------

             Summary: non-syntax error has unexpected category "PARSE ERROR"
                 Key: DRILL-2880
                 URL: https://issues.apache.org/jira/browse/DRILL-2880
             Project: Apache Drill
          Issue Type: Bug
          Components: SQL Parser
            Reporter: Daniel Barclay (Drill)
            Assignee: Aman Sinha
            Priority: Minor


Some errors that are not syntax errors (failures to match the productions of the SQL grammar),
such as referring to a non-existent table:

SELECT * FROM NoSuchFile;

yield error messages that unexpectedly refer to parsing, such as:

PARSE ERROR: From line 1, column 15 to line 1, column 26: Table 'NoSuchFile' not found
&nbsp;

That "PARSE ERROR" sounds like it's saying it's specifically a parsing error, when it's really
an error downstream of parsing.  

(A parsing error requires changing the query to conform to the grammar.  In the above case,
creating a file or view would resolve the problem without changing the query, so the problem
is not a parsing error.)
&nbsp;

Its not clear whether that error should be reported using a different existing or new error
category, or whether the category "PARSE ERROR" should be renamed (to cover both real parsing
errors and the level of errors).

Note, however, that to avoid confusion, errors that can be fixed by changing something other
than the query (i.e., the data store state) probably should not be reported using the same
category as true syntax/parsing errors.





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

Mime
View raw message