[ 
https://issues.apache.org/jira/browse/DRILL-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679275#comment-16679275
 ] 

ASF GitHub Bot commented on DRILL-6760:
---------------------------------------

lushuifeng commented on issue #1519: DRILL-6760: Retain original exception in 
Verbose Error Message
URL: https://github.com/apache/drill/pull/1519#issuecomment-436864699
 
 
   @arina-ielchiieva Changes are made according to your suggestions, could you 
please take another look? (Building job timeouts)
   
   Here is the comparison of before and after the change with the same query.
   ![screen shot 2018-11-08 at 11 19 
29](https://user-images.githubusercontent.com/1677203/48175789-6ebf9580-e348-11e8-9fe8-e91ab0c880a0.png)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> The Profiles page does not retain the original exception if the query fails
> ---------------------------------------------------------------------------
>
>                 Key: DRILL-6760
>                 URL: https://issues.apache.org/jira/browse/DRILL-6760
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Web Server
>    Affects Versions: 1.14.0
>            Reporter: Nitin Sharma
>            Assignee: shuifeng lu
>            Priority: Major
>             Fix For: 1.15.0
>
>
> The profiles page (that shows query execution for the most recently issued 
> queries) on the foreman node does not retain the original exception if the 
> query failed. The error always says "Remote Drill Exception" and gives an id. 
> The actual exception could be anything from OOM, s3 access errors, out of 
> disk issue etc but they seem to get swallowed. 
>  
> It is hard to debug if there are long running queries. 



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

Reply via email to