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/04/06 07:38:12 UTC

[jira] [Commented] (DRILL-2689) Parser does not report missing space between order by and limit keyword

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

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

A SQL <separator> is not usually required between a <nondelimiter token> (e.g., "]") and a <delimiter token> (e.g., the "LIMIT" keyword).

Is there some overriding rule that requires a space in the reported case?


> Parser does not report missing space between order by <key> and limit keyword
> -----------------------------------------------------------------------------
>
>                 Key: DRILL-2689
>                 URL: https://issues.apache.org/jira/browse/DRILL-2689
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: SQL Parser
>    Affects Versions: 0.9.0
>            Reporter: Khurram Faraaz
>            Assignee: Aman Sinha
>            Priority: Minor
>
> Note that the space between order by <key> and limit keyword is missing, the query is still executed and the missing space is not reported by the parser.
> {code}
> 0: jdbc:drill:> select columns[0] from `allTypData2.csv` order by columns[3]limit 3;
> +------------+
> |   EXPR$0   |
> +------------+
> | -2002649798 |
> | -31673369  |
> | -1777415979 |
> +------------+
> 3 rows selected (0.113 seconds)
> 0: jdbc:drill:> select columns[0] from `allTypData2.csv` order by columns[3] limit 3;
> +------------+
> |   EXPR$0   |
> +------------+
> | -2002649798 |
> | -31673369  |
> | -1777415979 |
> +------------+
> 3 rows selected (0.119 seconds)
> {code}



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