[ 
https://issues.apache.org/jira/browse/HIVE-16007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Vary updated HIVE-16007:
------------------------------
    Attachment: HIVE-16007.patch

The patch proposes two changes:
- Set the {{isLogBeingGenerated}} to false if there is an exception executing 
the statement
- Handle the interruption more agressively
-- When interrupt arrives then try to fetch the logs and then finish running 
the LogRunnable thread
-- We check the interruption status before fetching the logs, and if the thread 
is interrupted then fetch the remaining logs and exit. This prevents the 
possible active loop when we get an exception so we does not sleep, and will 
not get the InterruptedException even though the parent thread finished the 
statement execution

> When the query does not complie the LogRunnable never stops
> -----------------------------------------------------------
>
>                 Key: HIVE-16007
>                 URL: https://issues.apache.org/jira/browse/HIVE-16007
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>    Affects Versions: 2.2.0
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>         Attachments: HIVE-16007.patch
>
>
> When issuing a sql command which does not compile then the LogRunnable thread 
> is never closed.
> The issue can be easily detected when running beeline with showWarnings=true.
> {code}
> $ ./beeline -u "jdbc:hive2://localhost:10000 pvary pvary" --showWarnings=true
> [..]
> Connecting to jdbc:hive2://localhost:10000
> Connected to: Apache Hive (version 2.2.0-SNAPSHOT)
> Driver: Hive JDBC (version 2.2.0-SNAPSHOT)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> Beeline version 2.2.0-SNAPSHOT by Apache Hive
> 0: jdbc:hive2://localhost:10000> selekt;
> Warning: java.sql.SQLException: Method getQueryLog() failed. Because the 
> stmtHandle in HiveStatement is null and the statement execution might fail. 
> (state=,code=0)
> [..]
> Warning: java.sql.SQLException: Can't getQueryLog after statement has been 
> closed (state=,code=0)
> [..]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to