[
https://issues.apache.org/jira/browse/DRILL-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deneche A. Hakim updated DRILL-2675:
------------------------------------
Attachment: DRILL-2675.0.patch.txt
Initial patch with a working solution. This patch cleans the path for errors,
especially user errors with meaningful messages, to be propagated properly to
the client.
The patch includes changes to 2 existing use cases where the error message was
successfully improved.
The general idea is: if a code wants to throw an exception that contains a
meaningful error message, it throws a DrillUserException. The propagation code
will make sure this exception is propagated to the client. The user exception
object doesn't contain the final error message, but enough information about
the error, the client will use this information to display a better error
message.
Any exception that is not a DrillUserException (or one of it's subclasses) will
be considered as a system exception. For those exceptions the client will only
display the error id and drillbit identity in case the user wants to check the
logs for more informations about the error.
Error objects sent to the client will still contain a stack trace that can be
used to display more information if the client has enabled the error verbose
mode.
> Implement a subset of User Exceptions to improve how errors are reported to
> the user
> ------------------------------------------------------------------------------------
>
> Key: DRILL-2675
> URL: https://issues.apache.org/jira/browse/DRILL-2675
> Project: Apache Drill
> Issue Type: Sub-task
> Components: Execution - Flow
> Affects Versions: 0.9.0
> Reporter: Deneche A. Hakim
> Assignee: Deneche A. Hakim
> Fix For: 0.9.0
>
> Attachments: DRILL-2675.0.patch.txt
>
>
> Implement a set of most needed User Exceptions. Each user exception will
> contain:
> - a meaningful error message
> - optional context information (e.g. which file/row caused the error)
> - errorID and drillbit name, to help users and developers find the original
> error in the logs
> - a set of suppressed exceptions that were thrown along the original error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
