You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Bharathkrishna Guruvayoor Murali (JIRA)" <ji...@apache.org> on 2018/03/27 21:34:00 UTC
[jira] [Commented] (HIVE-19048) Initscript errors are ignored
[ https://issues.apache.org/jira/browse/HIVE-19048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416278#comment-16416278 ]
Bharathkrishna Guruvayoor Murali commented on HIVE-19048:
---------------------------------------------------------
I checked the code, and this seems to be the default behavior.
Also, there is a --force option in theĀ [Beeline commands|https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-BeelineCommands], which can be used to continue execution even after an error in the initFile.
> Initscript errors are ignored
> -----------------------------
>
> Key: HIVE-19048
> URL: https://issues.apache.org/jira/browse/HIVE-19048
> Project: Hive
> Issue Type: Bug
> Components: Beeline
> Reporter: Zoltan Haindrich
> Assignee: Bharathkrishna Guruvayoor Murali
> Priority: Major
>
> I've been running some queries for a while when I've noticed that my initscript has an error; and beeline stops interpreting the initscript after encountering the first error.
> {code}
> echo 'invalid;' > init.sql
> echo 'select 1;' > s1.sql
> beeline -u jdbc:hive2://localhost:10000/ -n hive -i init.sql -f s1.sql
> [...]
> Running init script init.sql
> 0: jdbc:hive2://localhost:10000/> invalid;
> Error: Error while compiling statement: FAILED: ParseException line 1:0 cannot recognize input near 'invalid' '<EOF>' '<EOF>' (state=42000,code=40000)
> 0: jdbc:hive2://localhost:10000/> select 1;
> [...]
> $ echo $?
> 0
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)