You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Daniel Barclay (Drill) (JIRA)" <ji...@apache.org> on 2015/05/05 21:12:01 UTC

[jira] [Commented] (DRILL-2229) SQL syntax errors should use SQLSyntaxErrorException

    [ https://issues.apache.org/jira/browse/DRILL-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529082#comment-14529082 ] 

Daniel Barclay (Drill) commented on DRILL-2229:
-----------------------------------------------

> Did you mean the exception which would be thrown when optiq parses input SQL string (which is SqlParseException)? 

I did (when I submitted that), but now with our change to UserException, this changes to "SQL syntax error should use UserException and its PARSE ERROR error type."

I don't know how much that has already been applied.  (If the answer is "mostly," then this JIRA report can probably be closed.   If the answer is just "somewhat," then maybe this JIRA should be retitled (to refer to PARSE ERROR).)


> SQL syntax errors should use SQLSyntaxErrorException
> ----------------------------------------------------
>
>                 Key: DRILL-2229
>                 URL: https://issues.apache.org/jira/browse/DRILL-2229
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: SQL Parser
>            Reporter: Daniel Barclay (Drill)
>            Assignee: Sean Hsuan-Yi Chu
>             Fix For: 1.2.0
>
>
> SQL syntax errors should be reported with SQLSyntaxErrorException (or subclasses, of course) rather than SQLException (in part so that when they get to the JDBC interface they can be reported at intended using SQLSyntaxErrorException .



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