You might want to hold off on running more complex queries temporarily... A
couple of issues that I am aware of:
1.  Aggregation queries will currently fail.. this is related to a conflict
between GroupingAggregate and CollapsingAggregate.  We only need one of
these.
2. There is likely an issue with case sensitivity of operator and function
names.  For example, the following queries fail currently.  If I modify the
FunctionRegistry to use lowerCase when checking a function, then these
queries work ok.

select * from dfs.`/tmp/parquet/nation.parquet` where N_NATIONKEY > 1 and
N_NATIONKEY < 3

message: "Failure while parsing sql. < ExpressionParsingException:[ Unable
to find function definition for function named \'AND\' ]





On Sat, Mar 8, 2014 at 9:12 AM, Yash Sharma <[email protected]>wrote:

> Awesome!!
> Works like charm. Thanks!! :)
>
> ________________________________________
> From: Mehant Baid [[email protected]]
> Sent: Saturday, March 08, 2014 10:32 PM
> To: [email protected]
> Subject: Re: Error while starting Sqlline on latest master
>
> Try using backquote (`) instead of the single quote (') for the table
> name like the following
>
> select employee_id, first_name from cp.`employee.json`;
>
> Thanks
> Mehant
>
> On 3/8/14, 8:42 AM, Yash Sharma wrote:
> > Hi All,
> > I was trying to run queries on Sqlline and am stumbling at this error.
> > I am on the latest master and have followed the installation notes on
> github (https://github.com/apache/incubator-drill/blob/master/INSTALL.md).
> >
> > Am I missing something?
> >
> > Regards,
> > Yash
> >
> >
> > 0: jdbc:drill:zk=local> SELECT employee_id, first_name FROM
> cp.'employee.json';
> > Query failed: org.apache.drill.exec.rpc.RpcException: Remote failure
> while running query.[error_id: "836beda1-e069-4efc-af67-82f5f0eb9e4a"
> > endpoint {
> >    address: "black-box"
> >    user_port: 31010
> >    control_port: 31011
> >    data_port: 31012
> > }
> > error_type: 0
> > message: "Failure while parsing sql. < SqlParseException:[ Encountered
> \". \\\'employee.json\\\'\" at line 1, column 39.\nWas expecting one of:\n
>    <EOF> \n    \"ORDER\" ...\n    \"LIMIT\" ...\n    \"OFFSET\" ...\n
>  \"FETCH\" ...\n    \"NATURAL\" ...\n    \"JOIN\" ...\n    \"INNER\" ...\n
>    \"LEFT\" ...\n    \"RIGHT\" ...\n    \"FULL\" ...\n    \"CROSS\" ...\n
>  \",\" ...\n    \".\" ...\n    \"AS\" ...\n    <IDENTIFIER> ...\n
>  <QUOTED_IDENTIFIER> ...\n    <BACK_QUOTED_IDENTIFIER> ...\n
>  <BRACKET_QUOTED_IDENTIFIER> ...\n    <UNICODE_QUOTED_IDENTIFIER> ...\n
>  \"TABLESAMPLE\" ...\n    \"WHERE\" ...\n    \"GROUP\" ...\n    \"HAVING\"
> ...\n    \"WINDOW\" ...\n    \"UNION\" ...\n    \"INTERSECT\" ...\n
>  \"EXCEPT\" ...\n    \".\" <IDENTIFIER> ...\n    \".\" <QUOTED_IDENTIFIER>
> ...\n    \".\" <BACK_QUOTED_IDENTIFIER> ...\n    \".\"
> <BRACKET_QUOTED_IDENTIFIER> ...\n    \".\" <UNICODE_QUOTED_IDENTIFIER>
> ...\n     ] < ParseException:[ Encountered \". \\\'employee.json\\\'\" at
> line 1, column 39.\nWas expecting one of:\n    <EOF> \n    \"ORDER\" ...\n
>    \"LIMIT\" ...\n    \"OFFSET\" ...\n    \"FETCH\" ...\n    \"NATURAL\"
> ...\n    \"JOIN\" ...\n    \"INNER\" ...\n    \"LEFT\" ...\n    \"RIGHT\"
> ...\n    \"FULL\" ...\n    \"CROSS\" ...\n    \",\" ...\n    \".\" ...\n
>  \"AS\" ...\n    <IDENTIFIER> ...\n    <QUOTED_IDENTIFIER> ...\n
>  <BACK_QUOTED_IDENTIFIER> ...\n    <BRACKET_QUOTED_IDENTIFIER> ...\n
>  <UNICODE_QUOTED_IDENTIFIER> ...\n    \"TABLESAMPLE\" ...\n    \"WHERE\"
> ...\n    \"GROUP\" ...\n    \"HAVING\" ...\n    \"WINDOW\" ...\n
>  \"UNION\" ...\n    \"INTERSECT\" ...\n    \"EXCEPT\" ...\n    \".\"
> <IDENTIFIER> ...\n    \".\" <QUOTED_IDENTIFIER> ...\n    \".\"
> <BACK_QUOTED_IDENTIFIER> ...\n    \".\" <BRACKET_QUOTED_IDENTIFIER> ...\n
>  \".\" <UNICODE_QUOTED_IDENTIFIER> ...\n     ]"
> > ]
> > Error: exception while executing query (state=,code=0)
> >
> > ________________________________
> >
> >
> >
> >
> >
> >
> > NOTE: This message may contain information that is confidential,
> proprietary, privileged or otherwise protected by law. The message is
> intended solely for the named addressee. If received in error, please
> destroy and notify the sender. Any use of this email is prohibited when
> received in error. Impetus does not represent, warrant and/or guarantee,
> that the integrity of this communication has been maintained nor that the
> communication is free of errors, virus, interception or interference.
>
>
>
> ________________________________
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential,
> proprietary, privileged or otherwise protected by law. The message is
> intended solely for the named addressee. If received in error, please
> destroy and notify the sender. Any use of this email is prohibited when
> received in error. Impetus does not represent, warrant and/or guarantee,
> that the integrity of this communication has been maintained nor that the
> communication is free of errors, virus, interception or interference.
>

Reply via email to