[
https://issues.apache.org/jira/browse/DRILL-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Altekruse updated DRILL-470:
----------------------------------
Component/s: Execution - RPC
> 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
> Components: Execution - RPC
> Reporter: Jason Altekruse
> Assignee: Jason Altekruse
> Fix For: 0.7.0
>
>
> 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
(v6.3.4#6332)
