[
https://issues.apache.org/jira/browse/HIVE-8396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006544#comment-15006544
]
Elliot West commented on HIVE-8396:
-----------------------------------
I notice that the command line input behaves differently compare with script
exectution with the {{-f}} option (0.14.0):
h4. Case 1: CLI entry fails
{code}
hive (default)> -- hello
> set x=1;
FAILED: ParseException line 2:4 missing KW_ROLE at 'x' near 'x'
line 2:5 missing EOF at '=' near 'x'
{code}
h4. Case 2: Script execution succeeds
{code}
[ewest@host]$ cat x.hql
-- hello
set x=1;
set x;
[ewest@host]$ hive -f x.hql
x=1
{code}
> Hive CliDriver command splitting can be broken when comments are present
> ------------------------------------------------------------------------
>
> Key: HIVE-8396
> URL: https://issues.apache.org/jira/browse/HIVE-8396
> Project: Hive
> Issue Type: Bug
> Components: Parser, Query Processor
> Affects Versions: 0.14.0
> Reporter: Sergey Shelukhin
>
> {noformat}
> -- SORT_QUERY_RESULTS
> set hive.cbo.enable=true;
> ... commands ...
> {noformat}
> causes
> {noformat}
> 2014-10-07 18:55:57,193 ERROR ql.Driver (SessionState.java:printError(825)) -
> FAILED: ParseException line 2:4 missing KW_ROLE at 'hive' near 'hive'
> {noformat}
> If the comment is moved after the command it works.
> I noticed this earlier when I comment out parts of some random q file for
> debugging purposes, and it starts failing. This is annoying.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
