You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Shohei Okumiya (Jira)" <ji...@apache.org> on 2025/04/14 06:09:00 UTC
[jira] [Resolved] (HIVE-20054) Propagate ExecutionExceptions from the driver thread to the client
[ https://issues.apache.org/jira/browse/HIVE-20054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shohei Okumiya resolved HIVE-20054.
-----------------------------------
Fix Version/s: NA
Resolution: Won't Fix
We have discontinued Hive on Spark and EoLed Hive 3. HIVE-26134
> Propagate ExecutionExceptions from the driver thread to the client
> ------------------------------------------------------------------
>
> Key: HIVE-20054
> URL: https://issues.apache.org/jira/browse/HIVE-20054
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sahil Takiar
> Priority: Major
> Fix For: NA
>
>
> In {{AbstractSparkClient}} we have the following code:
> {code:java}
> try {
> driverFuture.get();
> } catch (InterruptedException ie) {
> // Give up.
> LOG.warn("Interrupted before driver thread was finished.", ie);
> } catch (ExecutionException ee) {
> LOG.error("Driver thread failed", ee);
> }
> {code}
> If the driver {{Future}} throws an {{ExecutionException}} the error is simply logged, and a {{RuntimeException}} is thrown with the generic message "Error while waiting for Remote Spark Driver to connect back to HiveServer2."
> We should propagate the {{ExecutionException}} to the client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)