[
https://issues.apache.org/jira/browse/DRILL-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957405#comment-14957405
]
ASF GitHub Bot commented on DRILL-3927:
---------------------------------------
Github user adeneche commented on a diff in the pull request:
https://github.com/apache/drill/pull/199#discussion_r42029401
--- Diff:
exec/java-exec/src/main/java/org/apache/drill/exec/client/DrillClient.java ---
@@ -369,6 +378,10 @@ public void queryCompleted(QueryState state) {
private void fail(Exception ex) {
logger.debug("Submission failed.", ex);
+ final Throwable cause = ex.getCause();
+ if (cause != null) {
+ logger.debug("Submission failure cause.", ex.getCause());
--- End diff --
same comment related to
[DRILL-2692](https://issues.apache.org/jira/browse/DRILL-2692)
> Use OutOfMemoryException in more places
> ---------------------------------------
>
> Key: DRILL-3927
> URL: https://issues.apache.org/jira/browse/DRILL-3927
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Reporter: Chris Westin
> Assignee: Chris Westin
>
> The new allocator uses OutOfMemoryException in better ways; some additional
> exception handling sites need to catch and handle this exception in
> preparation for the new allocator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
