drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Altekruse (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DRILL-470) Add stack traces to drill error messages
Date Fri, 31 Oct 2014 01:27:33 GMT

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

Jason Altekruse resolved DRILL-470.
       Resolution: Won't Fix
    Fix Version/s:     (was: Future)

We have improved the error reporting to direct users to a particular nodes log files, this
is no longer needed.

> Add stack traces to drill error messages
> ----------------------------------------
>                 Key: DRILL-470
>                 URL: https://issues.apache.org/jira/browse/DRILL-470
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Jason Altekruse
>            Assignee: Jason Altekruse
> Errors occurring during drill execution currently only return the error message, not
the stack trace leading up to the error. Often time we are debugging errors that cannot be
meaningfully diagnosed without a stack trace. The current architecture is designed for a release,
where we would be wanting to hide the stack traces from users, but the current state of the
project would seem to make it more useful to include the stack trace until we reach GA. Current
solution is to use Lilith log viewer, while this does work, lilith can be a pain and is an
extra step needed almost any time a bug is explored.

This message was sent by Atlassian JIRA

View raw message