[
https://issues.apache.org/jira/browse/DRILL-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bohdan Kazydub updated DRILL-6724:
----------------------------------
Description: Sometimes when an error occurs it may be helpful to have
operator stack with context data along with original stacktrace to help
developers to track down a failure. To achieve this, each operator should
provide a context which can be dumped to logs. In the end of FragmentExecutor's
execution if the state is FAILED the operator stack will be dumped to logs
before exception stacktrace. (was: Sometimes when IndexOutOfBoundsException is
exposed to users it is not clear what causes the problem. Instead this
exception may be converted to a more useful UserException containing context
data like filename, line, position etc (depending on what is available from a
reader for a given type).
A possible approach is to add a method to a RecordReader interface which
produces UserException of type ErrorType.DATA_READ with context data, so that
when such an UserException is needed it can be easily obtained by invoking the
method.)
> Convert IndexOutOfBounds exception to UserException with context data where
> possible
> ------------------------------------------------------------------------------------
>
> Key: DRILL-6724
> URL: https://issues.apache.org/jira/browse/DRILL-6724
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.14.0
> Reporter: Bohdan Kazydub
> Assignee: Bohdan Kazydub
> Priority: Major
> Fix For: 1.15.0
>
>
> Sometimes when an error occurs it may be helpful to have operator stack with
> context data along with original stacktrace to help developers to track down
> a failure. To achieve this, each operator should provide a context which can
> be dumped to logs. In the end of FragmentExecutor's execution if the state is
> FAILED the operator stack will be dumped to logs before exception stacktrace.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
