Hi Thejas,

OK. I'll fix the problem and create a JIRA ticket.

Thanks.

2016年4月26日(火) 9:50 Thejas Nair <thejas.n...@gmail.com>:

> I agree it should show an error message instead of stack trace in this
> case.
>
>
> On Sat, Apr 23, 2016 at 3:56 AM, Takuma Wakamori
> <wakamori.tak...@gmail.com> wrote:
> > Hi all,
> >
> > This is my first post to developers' mailing list.
> >
> > I have a question about the behavior of HiveServer2.
> > When HiveServer2 parse invalid syntaxes sent from beeline2, it prints an
> > ParseException in console output.
> >
> > Example code is below.
> >
> > ----------------------------------
> > Input:
> > hostA$ hiveserver2
> > hostB$ beeline -u jdbc:hive2://localhost:10000 -n user -p pass -e
> "invalid
> > syntax;"
> >
> > Output:
> > hostA$ NoViableAltException(26@[])
> >
> >        [0/1248]
> >         at
> >
> org.apache.hadoop.hive.ql.parse.HiveParser.statement(HiveParser.java:1108)
> >         at
> > org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:204)
> >         at
> > org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:166)
> >         at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:444)
> >         at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:319)
> >         at
> > org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1199)
> >         at
> > org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1186)
> >         at
> >
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:146)
> >         at
> >
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:218)
> > ...
> > FAILED: ParseException line 1:0 cannot recognize input near 'invalid'
> > 'syntax' '<EOF>'
> > => Is it correct?
> >
> > hostB$ Error: Error while compiling statement: FAILED: ParseException
> line
> > 1:0 cannot recognize input near 'invalid' 'syntax' '<EOF>'
> > (state=42000,code=40000)
> > => correct.
> > ----------------------------------
> >
> > I feel strange about this behavior that it throws exception, because the
> > input text is invalid syntax but isn't an unexpected input.
> >
> > Is this correct design? If not, I will create the JIRA ticket and address
> > this issue to suppress the exception output.
> >
> > Thanks!
> > --
> > Takuma Wakamori
> > wakamori.tak...@gmail.com
>
-- 
Takuma Wakamori
wakamori.tak...@gmail.com

Reply via email to