You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Vineet Garg (JIRA)" <ji...@apache.org> on 2018/07/18 22:51:00 UTC

[jira] [Updated] (HIVE-18831) Differentiate errors that are thrown by Spark tasks

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

Vineet Garg updated HIVE-18831:
-------------------------------
    Fix Version/s: 4.0.0

> Differentiate errors that are thrown by Spark tasks
> ---------------------------------------------------
>
>                 Key: HIVE-18831
>                 URL: https://issues.apache.org/jira/browse/HIVE-18831
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Sahil Takiar
>            Assignee: Sahil Takiar
>            Priority: Major
>             Fix For: 4.0.0
>
>         Attachments: HIVE-18831.1.patch, HIVE-18831.2.patch, HIVE-18831.3.patch, HIVE-18831.4.patch, HIVE-18831.6.patch, HIVE-18831.7.patch, HIVE-18831.8.WIP.patch, HIVE-18831.9.patch, HIVE-18831.90.patch, HIVE-18831.91.patch, HIVE-18831.92.patch, HIVE-18831.93.patch
>
>
> We propagate exceptions from Spark task failures to the client well, but we don't differentiate between errors from HS2 / RSC vs. errors thrown by individual tasks.
> Main motivation is that when the client sees a propagated Spark exception its difficult to know what part of the excution threw the exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)